-
I'm not sure if this is still the case, but the original reason to have them be separate crates was because they needed to be dylib instead of rlib
I'd wager the "needs to be dylib" requirement is still true since the compiler does in fact have to load them dynamically
-
-
I assumed this goes away when you require them being const fn -- which started this. So you use a different mechanic to evaluate them at compile time
-
Oh right because they get interpreted. I suppose that's true. Though I don't think the compiler would be able to actually evaluate a function used to compile its own crate (e.g. the function would have not not call any other functions defined by the crate being compiled)
- 3 more replies
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.