You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2020. It is now read-only.
Something I'm constantly doing is casting values in cases where it's obvious and the compiler can easily infer the type based on the context. The proposal here is that we either have suffixes for each type, for instance u or s for annotating a signed and unsigned literal. Or we can infer the type of the literal based on the context of the expression.
I'm fine with either, or both, but I think not having any at all is a huge pain when writing code.
The text was updated successfully, but these errors were encountered:
That's not the primary reason of this issue.
The real issue is based on arithmetic or comparisons with certain types and literals. I'm pretty sure that a bug is what caused this, and had this have worked as intended, I wouldn't have made this issue.
In other words, this issue is now irrelevant, there are some bugs with arithmetic and comparisons on certain types I need to hunt down and report... unless this is how it's intended to be, in which case this issue still applies.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Something I'm constantly doing is casting values in cases where it's obvious and the compiler can easily infer the type based on the context. The proposal here is that we either have suffixes for each type, for instance
u
ors
for annotating a signed and unsigned literal. Or we can infer the type of the literal based on the context of the expression.I'm fine with either, or both, but I think not having any at all is a huge pain when writing code.
The text was updated successfully, but these errors were encountered: