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.

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

Ambiguous Coercions #496

Closed
DavePearce opened this issue Jun 4, 2015 · 1 comment
Closed

Ambiguous Coercions #496

DavePearce opened this issue Jun 4, 2015 · 1 comment
Labels
Milestone

Comments

@DavePearce
Copy link
Member

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).

@DavePearce
Copy link
Member Author

Since #495 is now implemented, this is resolved.

@DavePearce DavePearce added this to the v0.3.38 milestone Jan 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant