11–20 of 243 posts
> Introduces yet another non standardized, corporately backed Rust look-alike language.
What's gonna happen when we have 5 of these things crawling around, are they going to be compatible with each other?
var r : i32; How is this any better than int32_t r; ? all I see is additional, unnecessary keyword to type.
var r : i32; How is this any better than int32_t r; ? all I see is additional, unnecessary keyword to type.
var r : i32; How is this any better than int32_t r; ? all I see is additional, unnecessary keyword to type.
You type about the same number of characters. Now imagine you wanted to declare the value to be immutable.
The type omission version isn't very useful, as this type of code is difficult to read later. Generally end up regretting using auto, and end up converting it to the actual type, except with iterators or nasty templates.
var r : i32; How is this any better than int32_t r; ? all I see is additional, unnecessary keyword to type.
> Complains C++ evolution is too slow due to enforced standardizations by committee. > Introduces yet another non standardized, corporately backed Rust look-alike language. What's gonna happen when we have 5 of these things crawling around, are they going to be compatible with each other?
var r : i32; How is this any better than int32_t r; ? all I see is additional, unnecessary keyword to type.
You type about the same number of characters. Now imagine you wanted to declare the value to be immutable.
var r : i32; How is this any better than int32_t r; ? all I see is additional, unnecessary keyword to type.
abc * xyz;This might not be a huge issue for people reading code (because in context it should be pretty obvious), but for compiler it means that type information is required to parse code and compiler stages get mixed together.