veber-alex

15 ms·

211.
by veber-alex 4y ago
I don't see how that is all that different from Rust. The main difference I see is that in Rust it will also work with your own custom types, not just optional. fn make_bla() -> Option<Bla> { // this either r
212.
by veber-alex 4y ago
Go is not a systems programming language. I also personally find Go syntax to be horrible, especially now with generics.
213.
by veber-alex 4y ago
You linked to docs of 3 python projects and each one looks entirely different while the docs of all rust crates look exactly the same.
214.
by veber-alex 5y ago
I suggest you start reading the compiler error messages as they say exactly what trait is missing, no need to waste an hour. For example for this code: trait Foo { fn foo(&self) {} } struct Bar; impl Foo for Bar {}
215.
by veber-alex 5y ago
As mentioned in that github thread, this works in JetBrains IDEs. For rust-analyzer it's blocked on improvements in Chalk.
216.
by veber-alex 5y ago
You should not be using the RLS extension, it hasn't been updated in over a year. Instead you should use rust-analyzer which will soon become the official rust extension. https://marketplace.visualstudio.com/items?itemN
217.
by veber-alex 5y ago
cargo itself does need TOML support to build because cargo itself is a Rust crate [0]. But it's not a problem because you build a new version of cargo with an older version of cargo that of course can parse TOML. [0] https:/&#x2F
218.
by veber-alex 5y ago
The only thing new in Rust 2018 is the impl Trait in argument position. Generics and trait bounds are in the language from the start. So you can write this function like this: fn twiddle<T: IntoIterator<Item = Foozle>>(foozl