You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a method has been asynchronized, it will spawn and return a thread even if it has an invalid number of arguments. This is caused because the newly defined method accepts parameters through a splat operator. This is a minor issue, causing only a slight performance penalty when calling a method with the wrong number of arguments. The parameter information can be pulled, we should see if there's a way to use the actual information in the new method definition https://ruby-doc.org/core-2.2.0/Method.html#method-i-parameters.
The text was updated successfully, but these errors were encountered:
iCodeSometime
changed the title
An asynchronized spawns and returns a thread before giving an invalid argument error
An asynchronized method spawns and returns a thread before giving an invalid argument error
May 31, 2018
iCodeSometime
changed the title
An asynchronized method spawns and returns a thread before giving an invalid argument error
When called with too few arguments, an asynchronized method returns a thread before giving an invalid argument error
May 31, 2018
Description
When a method has been asynchronized, it will spawn and return a thread even if it has an invalid number of arguments. This is caused because the newly defined method accepts parameters through a splat operator. This is a minor issue, causing only a slight performance penalty when calling a method with the wrong number of arguments. The parameter information can be pulled, we should see if there's a way to use the actual information in the new method definition https://ruby-doc.org/core-2.2.0/Method.html#method-i-parameters.
Reproduction Steps
The text was updated successfully, but these errors were encountered: