3 ms·
I say this as a Rust enjoyer, but I think what most people mean when they say this is that there's a lot going on, especially in the function definition syntax.
by steinuil 2y ago
I say this as a Rust enjoyer, but I think what most people mean when they say this is that there's a lot going on, especially in the function definition syntax. When you start adding in lifetimes and generics with bounds, async, &muts, where clauses... it really does become unreadable. I don't really see a way to fix this without making the syntax even more verbose, or aggressively simplifying the type system to the point that function argument inference becomes viable, but then you might end up in a situation like Swift's where type checking a simple expression takes an excessively long time.
That and the colon-colons (::), probably. Those can add a lot of noise.
- majewsky 2y ago> colon-colons I prefer "quad-dot". Rolls off the tongue better. :)
- rob74 2y agoPaamayim Nekudotayim anyone (https://en.wikipedia.org/wiki/Scope_resolution_operator#PHP https://en.wikipedia.org/wiki/Scope_resolution_operator#PHP) ?
- alexey-salmin 2y agohttps://web.archive.org/web/20230713231438/http://bash.org/?925050 https://web.archive.org/web/20230713231438/http://bash.org/?... < Andys> oh dear < Andys> in ruby, symbols are represented with a prepended colon < Andys> eg. :flag < Andys> so some guy tshirt that said ":sex" < Andys> which everyone at railscamp knew meant "Sex symbol" < Andys> he wore it until someone pointed out that to non-rubyists it said "Colon sex"
- tormeh 2y agoI suspect the colon-colons were a mistake. Java uses periods for both modules and classes, and it doesn't seem to be a problem there. Lifetimes are really ugly. You usually don't need to write them explicitly, but that's not a real excuse.