miniblog.

← Back to all posts
Apr 9, 2016 at 18:42
Even in 2016, we're still exploring the best way to display CLI compiler errors. Some interesting iterations in Rust
Overhaul borrowck error messages and compiler error formatting generally by nikomatsakis · Pull Request #32756 · rust-lang/rust
Overhaul borrowck error messages and compiler error formatting generally by nikomatsakis · Pull Request #32756 · rust-lang/rust
This is a major overhaul of how the compiler reports errors. The primary goal is to be able to give many spans within the same overall context, such as this: ./borrow-errors.rs:73:17: 73:20: error:...

Related Posts

Jun 15, 2023 at 05:34
Porting my 2016 Rust project from getopts to clap, and it's amazing how far the ecosystem has come. clap gives me a nicer help, automatic value validation, and can even generate completions for shells! First screenshot is getopts, second is clap.
PhotoPhoto
Feb 2, 2023 at 16:18
I'm dusting off a Rust project from 2016, and it's striking how much the ecosystem has grown. For example, I used getopts then whereas clap is delightful and does so much now.
Aug 3, 2018 at 04:49
Emacs is still becoming *more* customisable over time! For example, in 2016, the backtrace function became a user-level function. https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=27cada035a79b633e856a437dd0e037acc1d61c6 This allows users to introspect, debug or write their own!
Move backtrace to ELisp using a new mapbacktrace primitive - emacs.git - Emacs source repository