I'm surprised 1.0 didn't have the error codes. Error codes should be table stakes for anything that produces errors, really (Looking at you, proprietary codebases where I was putting in error codes while other people were writing the C++ equivalent of `.expect("the value to be right")`)
I was a big advocate of adding error codes. I don't remember specifically the timeline, but we had so much stuff to do for 1.0, it doesn't surprise me that it got pushed back a bit.
At the time, I was thinking about the big old chunky Visual Basic manuals I used to own, and how useful those were.
> This implements the minimal scaffolding that allows mapping diagnostic messages to alpha-numeric codes, which could improve the searchability of errors. In addition, there's a new compiler option, `--explain {code}` which takes an error code and prints out a somewhat detailed explanation of the error.
committed on Jul 10, 2014
I think I've figured out what happened here: the particular error that was chosen didn't have a code until 1.2. The example from this commit does show a code on Rust 1.0.0: https://godbolt.org/z/14hcb3ETG
My recollection is that Brian Anderson, who came from the C# world, was an early advocate of the easily-googlable error codes that Microsoft compilers use a lot, and pushed to get them in. That was a good call. (In general Brian had a lot of behind-the-scenes positive influence on Rust: my favorite brson-ism is "if the code doesn't have a test it doesn't exist".)
Yeah this PR cites it as explicitly a continuation of Bryan’s work. I never did any implementation work on errors, I was just a big fan of the codes concept.
Not a movie but most motorsports do not follow the monomyth. The cars or trucks or tractors compete, but none of them are designated protagonist. The progression is usually from slower and cheaper vehicles to more expensive and faster ones, to build excitement for the audience.
The adventure of the individual vehicle is that it prepares for the races, it practices, it tunes, then it competes, and then it either wins or loses. And then, budget permitting, it prepares for the next race.
This can be generalized to stories about any kind of real-life racing. For example, there's a whole genre of videos about the history of speedrunning video games (competing to complete the game in the fastest time), popularized by the works of Youtuber SummoningSalt:
These are presented in an entertaining way that's full of twists and drama, but because they're non-fiction they can't be forced into any pre-existing structure.
This reminds me of Dwarf Fortress, a game famous for its auto-generated stories. Boatmurdered is one such story—it’s brutal, fascinating, it’s in this uncanny valley halfway between random and an actual story. And it definitely isn’t formulaic (except for the fact that everyone always dies in the end; the game’s motto is Losing is Fun).
SUSE just linked to the git repository's web UI, and remarked there are random 502 errors happening; probably so they're not notified about "broken links".
[edit] From the "<meta name="description">" tag (I noticed the nice slug when I shared the link with a friend):
Screen is the traditional terminal multiplexer software used on Linux and Unix systems. We found a local root exploit in Screen 5.0.0 affecting Arch Linux and NetBSD, as well as a couple of other issues that partly also affect older Screen versions, which are still found in the majority of distributions.
Everyone else is excuses as paper thin as a kid trying to get a cookie
reply