4 ms·
Maybe I’m not reading carefully enough, but if you have to specify non-pure macros yourself, how do you know when you didn’t do that correctly?
by nixpulvis 3y ago
Maybe I’m not reading carefully enough, but if you have to specify non-pure macros yourself, how do you know when you didn’t do that correctly?
- AndrewDucker 3y agoI think that you'd either need a way to programmatically recognise the ones that are pure, or to make it opt-in by each crate.
- estebank 3y agoI'm another comment I mention an alternative to "believing" then proc macro author. https://news.ycombinator.com/item?id=39808525 https://news.ycombinator.com/item?id=39808525
- nixpulvis 3y agoI was thinking more like hazard detection where it spins off side jobs running things in the cache and propagates the output if it doesn’t match. Would require a lot more processing but would hopefully still allow for faster builds. Having marked pure functions would be ideal though, no doubt.