Skip to content

Reject invalid operator names for implicit object calls#15526

Merged
straight-shoota merged 3 commits intocrystal-lang:masterfrom
nobodywasishere:nobody/reject-implicit-assignment-call
Mar 19, 2025
Merged

Reject invalid operator names for implicit object calls#15526
straight-shoota merged 3 commits intocrystal-lang:masterfrom
nobodywasishere:nobody/reject-implicit-assignment-call

Conversation

@nobodywasishere
Copy link
Contributor

Closes #10824

@HertzDevil
Copy link
Contributor

What about .&&? I don't think that's an assignment operator

@straight-shoota straight-shoota added kind:bug A bug in the code. Does not apply to documentation, specs, etc. topic:compiler:parser labels Feb 26, 2025
@nobodywasishere
Copy link
Contributor Author

Updated, should catch all the edge cases mentioned in the issue

@ysbaddaden ysbaddaden added this to the 1.16.0 milestone Mar 18, 2025
@straight-shoota straight-shoota merged commit 6c950ba into crystal-lang:master Mar 19, 2025
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind:bug A bug in the code. Does not apply to documentation, specs, etc. topic:compiler:parser

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parser does not reject invalid operator names for implicit object calls

5 participants