3 ms·
I think it's good to think outside the box. Maybe incorporating some tried and true Unicode would make sense. However, I don't think the issue is ASCII but rat
by vitiral 5y ago
I think it's good to think outside the box. Maybe incorporating some tried and true Unicode would make sense.
However, I don't think the issue is ASCII but rather consistency. I'm making a C-competetor language and using "c-like syntax" except I'm enforcing consistency. () is always one or more statements, with the last expression returning the value. {} is always representing concrete data like a struct, array or function args/result. []? That's a piece of a type name, allowing the developer to name something Foo[U32; Str]
fn foo: {a: U32, b: Str} -> U32 (
if a > 5 then b + "is greater then 5"
else b + "lte 5"
)
)