Aria Desires

yep, #9 discusses the way I would do that with a slant more towards tests being shared between projects

Main problem to solve is properly buffering up compiler messages. Right now things are fairly interactive (although CC is annoyingly prone to spitting out tons of stuff on the assumption...

That's probably the simplest/best approach. Main alternative is to do some upstream work to make cc-as-library-but-not-in-build.rs more usable.

I should document this better: the test harness will created a `generated_impls` dir whose structure and file names reflect the test cases. All of the source code being used is...

For the godbolt usecase you wouldn't actually need anything to "work" right? You can just have one side calling a forward-declared extern, and the other side just declaring a function?

I was assuming the typical usecase you were interested in was mixed-compiler (e.g. clang_calls_gcc), and so you would have two files using two separate "compilers" in godbolt, one for the...

Ooh fun, good tip!

I'd also note I'm getting a bit burnt out on collection code-review, which I find much more intensive than reviewing other kinds of changes. It's subtle, complicated, and often brushes...

I have made https://github.com/contain-rs (shout-outs to cmr for the fantastic pun).

Crates to make: - [x] compare (done, unpublished atm, not sure about crate naming/ownership story) - [x] tree (should map and set be separate crates...?) - [x] trie (should map...