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

Least upper bounds issues #62

Open
christydennison opened this issue Jul 9, 2013 · 0 comments
Open

Least upper bounds issues #62

christydennison opened this issue Jul 9, 2013 · 0 comments
Labels

Comments

@christydennison
Copy link
Contributor

Located at Data and Control Flow > Type Inference > Least Upper Bounds (LUB)

Define LUB before you use it. Best to define acronyms before you use them, even if it is the acronym of the title.

Section's example of weak conformance is not clear. Does this mean I can convert a char to an Int if they weakly conform? What is the relevance of LUB? Maybe say that you can convert a char to an Int because a char is only two bytes, and an Int is 4, so you don't lose information by converting one to the other. However, it's "weak" conformance because char and Int can only be converted to one another, and don't have other properties that you'd have in "strong" conformance, such as ???.

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