Sebastian Dröge
Sebastian Dröge
Apart from increasing build times, it also wouldn't solve the problem. `mymacro.rs` might use the same Rust dependency as some other non-native Rust target, so you would have to also...
No, they're normal Rust code that is compiled into a shared library that can then be loaded by the compiler :)
@xclaesse Maybe another solution here would be to simply convert cargo projects to two dependencies (or maybe even two subprojects?). One would be compiled natively, the other not. And proc-macro...
If there's more use-cases of this than Rust proc-macros that makes sense, sure :)