[fix] rename RubyHash#set(get) to avoid collision#9459
Merged
Conversation
Groovy's `map['foo'] = 10` "set-property" protocol would end up picking up the `set(int, xxx)` as the setter instead of doing a `Map#put`
headius
approved these changes
Jun 13, 2026
headius
left a comment
headius
left a comment
Member
There was a problem hiding this comment.
These were new methods in 10.1 and never exposed publicly so this is a good clean fix. Unfortunate that Groovy exposes protected methods through its set-property protocol, but there's nothing we can do about that.
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
2 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.
Groovy's
map['foo'] = 10"set-property" protocol would end up picking up theset(int, xxx)as the setter instead of doing aMap#puthopefully, closing #9393