Brendan Zabarauskas

Yeah - thinking of how rustc normally renders errors. Maybe an option like `highlight_source` or something 🤔

Yeah, this has been requested before (See #285)! Perhaps this is something we should have a look at. For this specific instance, I'm wondering if using the notes section would...

Yeah, I agree it's a bit confusing. There are a bunch of `expect`s internally that can trigger if the source ranges and file ids are broken - I would rather...

Oh wow, this looks like a nice thing to learn from in general!

Would this be ok? ``` error[no-empty]: Empty block statements are not allowed ┌─ tests\main.js:1:5 │ 1 │ try { │ ╭───────^ 2 │ │ 3 │ │ } catch (e...

Yeah I'm really not a fan of either of those options TBH. In the first case you'd have a single character that is a different colour from the rest. In...

Rustc has a `--message-format short` mode too, which effectively looks like: ``` FizzBuzz.fun:8:12: error[E0308]: `case` clauses have incompatible types FizzBuzz.fun:15:16: error[E0308]: `case` clauses have incompatible types ```

That sounds _really_ cool! I like it! It would be nice if we offered the screen-reader support out of the box, but then allow people to build their own tools...

Sorry for the lack of updates on this, it's been a while! This is definitely a bit annoying. It would be helpful to know what any proposal would look like...

I mean, we have `SimpleFiles` which uses `()` for the file id?