Handle new eval source location #200
Merged
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
See https://bugs.ruby-lang.org/issues/19755 In Ruby 3.3, using `eval` without providing a source location will now default to `"(eval at #{__FILE__}:#{__LINE__})"`.
casperisfine
force-pushed
the
update-eval-location
branch
from
40ef63c to
8e50764
Compare
schneems
approved these changes
Jul 20, 2023
Collaborator
schneems
left a comment
schneems
left a comment
There was a problem hiding this comment.
That seems perfectly reasonable. Thank you for the patch. Looks good. Merging!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See https://bugs.ruby-lang.org/issues/19755
Ref: ruby/ruby#8070
In Ruby 3.3, using
evalwithout providing a source location will now default to"(eval at #{__FILE__}:#{__LINE__})".cc @schneems @nobu @hsbt