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
The names Uint and Float stem from Weird Things C Did(™) and so I think they should be renamed to more sensible names.
Unsigned integers are better called naturals so Uint should be renamed to Nat.
The name is abbreviated to 3 letters because it's a common type, just like Int.
I've seen this name used in a few places in functional programming languages.
It looks much better with all types using PascalCase in the language.
Explicit sized versions are Nat8, Nat16, Nat32, Nat64.
Floats are better called reals, so Float should be renamed to Real.
One opposing thought is that fixed-point numbers exist. Thus we should maybe have Float be renamed to Real as a "sensible default", but not so much sized types Float32 and Float64.
The "unsigned integer" to "natural" change will also make unsigned integers have equal importance as signed integers. Signedness will no longer sound like an opt-out; after all, tsuki treats integers and naturals as completely different types (though implicit widening conversions from naturals to integers may be permitted in the future, as they're fully sound).
The text was updated successfully, but these errors were encountered:
The names
Uint
andFloat
stem from Weird Things C Did(™) and so I think they should be renamed to more sensible names.Uint
should be renamed toNat
.Int
.PascalCase
in the language.Nat8
,Nat16
,Nat32
,Nat64
.Float
should be renamed toReal
.Float
be renamed toReal
as a "sensible default", but not so much sized typesFloat32
andFloat64
.The "unsigned integer" to "natural" change will also make unsigned integers have equal importance as signed integers. Signedness will no longer sound like an opt-out; after all, tsuki treats integers and naturals as completely different types (though implicit widening conversions from naturals to integers may be permitted in the future, as they're fully sound).
The text was updated successfully, but these errors were encountered: