What is the best way to test "compiler-heavy" code in @rustlang?
Making sure that certain constructs (e.g. procedural macro applied to a struct) compile or that certain combinations DO NOT compile.
The only thing I have found so far is compiletest_rs, should I start from there?
-
-
I opened a thread in the internals forum, let's see if there is any opening.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Typenum will hopefully soon be obsoleted by const generics, which should allow far better error messages. There are a few ways one can customize error messages, via special macros or annotations (e.g. `#[must_use(..)]`), but they cannot easily be applied to things like typenum.
-
Yes, Typenum should be superseded, quite exciting! But for projects like Frunk I don't see any major improvement on the horizon.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Writing about stuff to learn how it works, mostly in Rust.
Lead Engineer at