I commented on the commit, but I disagree with making worse backtraces the default. If you know what you're doing and want fast startup in exchange for worse backtraces, you can use --precompiled=yes (and we should probably document that more clearly), but for the sake of all of those users who don't know what they're doing, we can't make bad backtraces the default behavior.
On Monday, August 10, 2015 at 10:49:51 AM UTC-7, Simon Danisch wrote: > > Ah okay, I suspected this. I wasn't convinced though. > I compared the stack traces for precompiled=yes/no for the cases that > really annoyed me and it seemed precompiled=no never gave better results. > Guess I haven't hit the edge cases yet. > But given these findings, I would greatly prefer precompiled=yes as the > default, and if I'm unhappy with the stack traces I would want to switch to > precompiled=no temporarily. > I'll comment on the PR. > > > Am Montag, 10. August 2015 16:17:17 UTC+2 schrieb J Luis: >> >> On Windows here. >> Some months ago the local build with MinGW used to start almost >> instantaneously. Now it takes almost 4 seconds again. >> >
