We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The compiler currently detects ambiguous coercions, such as the following:
type R1 is {real x, int y} type R2 is {int x, real y} type R3 is {int x, int y} method f(R3 x) -> (R1|R2): return (R1|R2) x
However, I am concerned as to whether the algorithm is actually complete or not. For example, is it complete in the presence of recursive types?
This issue is relevant to the question as to whether or not to keep real types (#495).
real
The text was updated successfully, but these errors were encountered:
Since #495 is now implemented, this is resolved.
Sorry, something went wrong.
No branches or pull requests
The compiler currently detects ambiguous coercions, such as the following:
However, I am concerned as to whether the algorithm is actually complete or not. For example, is it complete in the presence of recursive types?
This issue is relevant to the question as to whether or not to keep
real
types (#495).The text was updated successfully, but these errors were encountered: