Re:I stopped everything and started writing C again
by jacksnipe on Wednesday March 12, 2025 @05:17PM
(#43347768)
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.
[ Parent
| on HN ]
Re:I stopped everything and started writing C again
by shakna on Wednesday March 12, 2025 @05:42PM
(#43347954)
I'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.
Re:I stopped everything and started writing C again
by knowitnone on Wednesday March 12, 2025 @08:44PM
(#43349293)
except nobody has to cater to every worst case scenario
Re:I stopped everything and started writing C again
by shakna on Wednesday March 12, 2025 @10:46PM
(#43349928)
So every disabled programmer is now a "worst case scenario"?
Re:I stopped everything and started writing C again
by SunlitCat on Thursday March 13, 2025 @03:15PM
(#43356389)
Or in short, Rust isn't for disabled programmers?
Re:I stopped everything and started writing C again
by BlarfMcFlarf on Thursday March 13, 2025 @10:42AM
(#43353881)
I am sure the Rust community would welcome feedback from blind developers about their error messages. Accessibility is a good thing.
Re:I stopped everything and started writing C again
by steveklabnik on Thursday March 13, 2025 @12:36PM
(#43354950)
One 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
I'm not aware of an existing tool to produce blind-friendly output, but this would at least be a part of that!