Skip to content

Operator overload #2761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
HerrCai0907 opened this issue Oct 8, 2023 · 1 comment · Fixed by #2762
Closed

Operator overload #2761

HerrCai0907 opened this issue Oct 8, 2023 · 1 comment · Fixed by #2762
Labels
breaking change enhancement

Comments

@HerrCai0907
Copy link
Member

HerrCai0907 commented Oct 8, 2023 •
edited
Loading

new A() == new B() and new B() == new A() will call different operator overload functions if both A and B have overload function declarations.

It needs more clear rules to handle it.
In my opinion there are two solutions:

  1. Diagnose when confused overload resolution.
  2. Define priorities and do overload resolution according to priorities.
@CountBleck
Copy link
Member

Number one seems more plausible, since a cast would fix it.

@HerrCai0907 HerrCai0907 mentioned this issue Oct 8, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking change enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: strictly check operator overload ambiguity HerrCai0907/assemblyscript
2 participants
@HerrCai0907 @CountBleck