Repository navigation
馃 Improved SequenceSet implicit integer coercion - #783
Merged
Merged
Conversation
This gives errors that are a little bit closer to ruby core and stdlib, when implicit integer arguments are expected. Unfortunately, although ruby's CAPI handles this (via macros like `NUM2LONG`), ruby doesn't expose a standard _ruby_ API to do it! In addition to raising errors that are more similar to core ruby APIs, this also handles `nil` arguments differently from unsent arguments.
Base automatically changed from
sequence_set/fix-slice-with-negative-length
to
master
October 10, 2026 03:25
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This gives errors that are a little bit closer to ruby core and stdlib, when implicit integer arguments are expected.
Unfortunately, although ruby's CAPI handles this (via macros like
NUM2LONG), ruby doesn't expose a standard ruby API to do it!In addition to raising errors that are more similar to core ruby APIs, this also handles
nilarguments differently from unsent arguments.