-
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)
-
-
Yeah I guess that could lead to some fun error messages!
-
https://gist.github.com/sgrif/7e28000d05f43899e68346f0f00d20a9 … is obviously the most pathological example. But I think it's way more insidious. If we let these functions call any code that was generated by a macro we're leaking compiler internals, since they're now dependent on order of evaluation
- 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.