It used to be that every few weeks I would see someone complaining about "wall of text" output from rust, but since we started trimming type names I haven't really seen any. The timing also roughly coincides with Twitter's demise and me not jumping on BlueSky, so it could be that I just lack the visibility I used to have. If you see any, feel free to ping me as I would like to keep knowing about these.
[#]RustLang #Rust
=> More informations about this toot | More toots from ekuber@hachyderm.io
But if it is not just a lack of visibility, then what people were put off by is not error verbosity (a lot of text) but rather useless verbosity (50 lines of text to name a type, sometimes in multiple places). It confirms my biases that we need to keep the information density high, not the textual output short.
=> More informations about this toot | More toots from ekuber@hachyderm.io
@ekuber The main grippe I have that sounds like "wall of text" is the ordering of errors and warnings. I often see the following:
When refactoring, there can be a lot of warnings (dead_code) and the only thing I care about is often the first error, but I often have to scroll to see it. Bacon fixes that though.
=> More informations about this toot | More toots from sgued@pouet.chapril.org
@sgued the second case shouldn't happen and should be reported as bugs
=> More informations about this toot | More toots from ekuber@hachyderm.io
@ekuber I didn't know that. I will keep in mind when encountering this in the future and open tickets. I see it sometimes when one error causes type inference to break someplace down the chain, and I don't know how the compiler would be able to "guess" that the errors are caused one by the other. My current holiday project involves a lot of macros, so a syntax error in the macro can lead to the macro outputting compile_error and the compiler can't guess that it's what's causing the errors.
=> More informations about this toot | More toots from sgued@pouet.chapril.org
@sgued @ekuber the compiler is able to insert a special “error” type into type inference so it can use that to determine when one error might be caused by another. It’s not always possible to determine one error is caused by another, but it’s almost always possible to do better.
=> More informations about this toot | More toots from porglezomp@mastodon.social
@porglezomp @sgued to give you an idea of the things we can do
https://github.com/rust-lang/rust/pull/133937
=> More informations about this toot | More toots from ekuber@hachyderm.io This content has been proxied by September (3851b).Proxy Information
text/gemini