4 ms·
Since it's underlining code you wrote, it must be "found" that is highlighted, not "expected". Much like up and down, gravity exists to ground all of us in the
by jacksnipe 2y ago
Since it's underlining code you wrote, it must be "found" that is highlighted, not "expected". Much like up and down, gravity exists to ground all of us in the same direction.
- shakna 2y agoI'm over here with TTS: Underlining in a terminal rarely translates to audio. It isn't the only consideration that needs to be made, when making things clear.
- knowitnone 2y agoexcept nobody has to cater to every worst case scenario
- shakna 2y agoSo every disabled programmer is now a "worst case scenario"?
- SunlitCat 2y agoOr in short, Rust isn't for disabled programmers?
- BlarfMcFlarf 2y agoI am sure the Rust community would welcome feedback from blind developers about their error messages. Accessibility is a good thing.
- steveklabnik 2y agoOne thing that could help here is that the compiler is able to offer output in JSON, allowing you to format the messages however you'd like: https://doc.rust-lang.org/rustc/json.html https://doc.rust-lang.org/rustc/json.html I'm not aware of an existing tool to produce blind-friendly output, but this would at least be a part of that!
- jacksnipe 2y agoI hadn’t considered this use case, thank you for pointing it out!