Skip to content

Conversation

wetneb
Copy link

@wetneb wetneb commented Jul 22, 2025

Closes #252 by making it possible to parse things like:

obj->operator==(4);
obj.operator<(3);

which are currently rejected.

@wetneb
Copy link
Author

wetneb commented Jul 22, 2025

I just realized #253 also tackled this problem - I hope one of the two solutions can be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: Parsing error with explicit calls to operator overloads
1 participant