I know we usually have the debugger in front of us - but sometimes a trace or log is required to see where code crashes. Think of a headless situation in a webserver or a small device like the pi where you want to reduce the performance overhead.
This leads to several questions: - Is something like this feasible/already possible in Pharo? - Any pointers on how Opal does optimizations? Do we have similar optimizations (removing code that could not be reached) that could be used.
The only optimisation we do is that we do not compile a push pop for variables (and even blocks) that are compiled for âeffectâ as there is no effect⦠One could of course add support for a special case like that. But what I donât really like is that all this would require explicit recompilation⦠and it would be always global⦠Marcus