On May 6, 2009, at 8:02 AM, Michele Simionato wrote:
Because the module macro-helper could have side-effects, such as registering objects at compile time (I am still thinking of the use cases in the Compilable and Composable Macros paper)
So, we're making all this fuss about the case that happens 1% (according to you [1]) of the time, out of which 90% (according to me [2]) have solutions that do not involve side effects, right? If that's true, then I'm kinda upset for all this wasted energy over a non issue. Aziz,,, [1] On May 5, 2009, at 8:16 AM, Michele Simionato wrote:
Finally, there the issue of modules which are just imported for side effects. This happens 1% of the times, is tricky, I did not think of it and I realized only yesterday the consequences (basically, it makes it harder to use Matthew Flatt's trick to manage side-effects at compile time).
[2] On May 5, 2009, at 10:43 AM, Abdulaziz Ghuloum wrote:
For 90% of these 1% of programs, there is probably another solution to the problem that does not involve side effects and forced evaluations.
