Skip to content

Conversation

@wetneb
Copy link
Contributor

@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
Contributor Author

wetneb commented Jul 22, 2025

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

@jdrouhard jdrouhard force-pushed the explicit_calls_to_overloaded_operators branch from 38d434f to 3462ab8 Compare September 16, 2025 00:43
@jdrouhard
Copy link
Collaborator

If you update, please hard reset your branch, I re-did the generate commit to use ABI 14 and the tree-sitter-cli dependency from the package.

Thanks for the fix.

@jdrouhard jdrouhard force-pushed the explicit_calls_to_overloaded_operators branch from 3462ab8 to e121126 Compare September 16, 2025 00:52
@jdrouhard jdrouhard merged commit 2a682d3 into tree-sitter:master Sep 16, 2025
3 of 4 checks passed
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

2 participants