While the language can be hard to get used to, the error messages are mostly great.
But sometimes you can send it on a goose chase with impossible type inference.
This is pretty cool. But my question is if the compiler knows it’s basically the same thing visually, why doesn’t it treat it the same way as far as syntax and just make them functionally equivalent;
Rust’s compiler is pretty much the reason the language gets so much praise. The borrow checking of course is the major reason, but it’s great at hints too.
My IDE says:
'(', '+', '-', '.', ';', <operator>, '[' or '}' expected, got ';'But the rust compiler explains
error: unknown start of token: \u{37e} help: Unicode character ';' (Greek Question Mark) looks like ';' (Semicolon), but it is not``` what a killjoy.If this is true then rust deserves all the praise it gets
While the language can be hard to get used to, the error messages are mostly great.
But sometimes you can send it on a goose chase with impossible type inference.
This is pretty cool. But my question is if the compiler knows it’s basically the same thing visually, why doesn’t it treat it the same way as far as syntax and just make them functionally equivalent;
Because then logically extending this you end up with JavaScript, where “1”==1 and it’s super hard to reason about what will/should happen
Rust’s compiler is pretty much the reason the language gets so much praise. The borrow checking of course is the major reason, but it’s great at hints too.