This repository was archived by the owner on May 26, 2020. It is now read-only.
more strict arguments handling, changed NoMethodError behavior #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arguments now strict in it's count, so if you defined UNBOUD in pattern then you have to match it in arguments ALL pattern now will be matched as usual ruby variable agrument method (*args)
|
|
jdantonio
added a commit
that referenced
this pull request
Sep 2, 2015
more strict arguments handling, changed NoMethodError behavior
Owner
|
@cvb Thank you! :-) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
arguments now strict in it's count, so if you defined UNBOUD
in pattern then you have to match it in arguments
ALL pattern now will be matched as usual ruby variable agrument
method (*args)
good news, now you can throw
NoMethodErrorandArgumentErrorfrom method body whenever you wantbad news it's not back compatible with previous version and little different in it's behaviour because now you have to handle all argments, that are able to bound
anyway this is more like illustration of what I told about in ticket, so any critique and suggestions are welcome, I'm not really sure how it should be done
#20