Skip to content
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

Actually keep track of *why* a type is not viable, for diagnostics. #17

Open
rymiel opened this issue Jul 13, 2022 · 0 comments
Open

Actually keep track of *why* a type is not viable, for diagnostics. #17

rymiel opened this issue Jul 13, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@rymiel
Copy link
Member

rymiel commented Jul 13, 2022 

  // TODO(rymiel): Actually keep track of *why* a type is not viable, for diagnostics.

https://github.com/yume-lang/yume/blob/164fcf0a3c9a763868eca3f3a1cf4d511f1b7e46/src/yume/semantic/overload.cpp#L174
@rymiel rymiel added the enhancement New feature or request label Jul 13, 2022
rymiel added a commit that referenced this issue Dec 28, 2022
@rymiel
All overload rejections now have diagnostics
4ff30ef 
Note that the specific reason for a compatibilty failure is not tracked,
which is what #17 tracks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rymiel