I did this on rust-ctor for a bit, but reverted to a stub proc macro that delegates to a real macro after a while. I think it's a worthwhile idea but the lack of a "cargo gen" command is what kills it IMO.

I suspect I'll find a use for this. Nice crate!

Sooooo long story short it was actually a bug in my 8051 emulator

Ah! I misunderstood. Totally makes sense.

FWIW I think it would be awesome if rustdocs _could_ generate a stable JSON output format for other shenanigans, however. :)

Isn't it just diagnostics though, not the actual rustdocs? IIRC there is at least one project out there that does codegen this way, but it slipped my mind, hah

Good guess! You're right that it's a bit problem. It's somewhere in my emulator but I don't know for sure. I suspect there's something really weird about how bits are allocated to chars onscreen.

The only syntax thing I dislike is shift operators alongside 'as' - gets kinda bracket heavy - but I grew to love the turbofish.

Always

I ported ctor over to a syn-free proc macro to do my part but I feel like that effort was just so, so painful.

Macros are in dire straits and really need a 2.0, even if the 2.0 isn't perfect.

The saddest part of the whole story that's kind of glossed over is that all this drama is yet again because of the American Health Care System.

A few years ago I additionally learned that `/usr/bin/time` is different from the bash builtin time. :/