-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Match out of range ArgumentError message with MRI #1774
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed in general we should match MRI exception messages for compatibility, unless there is a good reason no to (pretty rare).
b07ff12
to
96b24bc
Compare
Added the CHANGELOG entry |
@rafaelfranca Could you rebase this PR on top of current master (which has the CHANGELOG fixes)? |
96b24bc
to
f38d3ca
Compare
Done |
f38d3ca
to
176d2c3
Compare
PullRequest: truffleruby/1094
Merged, thanks. |
Yeah.... I found that too but chose to not spec it since our behavior would be different. The reason for that behavior is that MRI uses 4 bits to store the value for month. If the value is inside the 0-15 range it can be stored in the struct and later checked against the range of valid months. If the value is outside that range it will raise an error earlier. |
Interesting, thanks for the explanation and links. |
Active Support is asserting on this message, so I thought we could get it to match.
Shopify#1