-
Notifications
You must be signed in to change notification settings - Fork 326
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.
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
Compiler crash when ambiguous from
conversions are encountered
#7853
Comments
Radosław Waśko reports a new STANDUP for yesterday (2023-11-07): Progress: Added tests. Implemented a workaround that fixes the symptoms - but not the root cause yet. Searching for the root cause. It should be finished by 2023-11-10. Next Day: Next day I will be working on the same task. Dig to look for the root cause and try to fix that instead of a workaround. |
Radosław Waśko reports a new STANDUP for yesterday (2023-11-08): Progress: Found the cause in TreeToIR and created a proper fix. Added some more test cases. Removed workaround. Prepared the PR. Testing Pavel's Graal 21 migration on Windows. It should be finished by 2023-11-10. Next Day: Next day I will be working on the same task. Get the PR merged, start work on anti-join. |
I wanted to see what currently happens when the user defines 'colliding' from converions (i.e. conversions for the same type from the same type).
Currently, this code crashes the compiler with the following stack trace:
If I comment out any of the two conversions, it works fine, e.g.:
So it seems that the compiler cannot handle seeing two colliding conversions next to each other.
The text was updated successfully, but these errors were encountered: