Re: [racket-users] How to improve compile times?

2017-05-03 Thread Daniel Brunner
Am 28.04.2017 um 08:07 schrieb Alex Harsanyi: > > In the end, the start up time does not bother me too much, as it is a GUI > application and I spend a lot of time using it after starting it up, so the 7 > second wait is acceptable. I have other, more interesting, application > features to

Re: [racket-users] How to improve compile times?

2017-04-28 Thread Alex Harsanyi
On Friday, April 28, 2017 at 10:04:52 PM UTC+8, Matthew Flatt wrote: > I notice that your code calls `running-stickman-icon` on startup, which > takes about 2 seconds on my machine. Well, this is embarrassing for me. I remember adding that code in and having to decide on whether to wait 2

Re: [racket-users] How to improve compile times?

2017-04-28 Thread Matthew Flatt
At Thu, 27 Apr 2017 23:07:01 -0700 (PDT), Alex Harsanyi wrote: > > * The size of the bytecode does matter (and switching to Chez scheme's > run-time could hopefully improve that) > > All the .zo files put together are about 4Mb. I'm not sure if this is big or > not? 4MB is not big. But your

Re: [racket-users] How to improve compile times?

2017-04-28 Thread Matthew Flatt
At Thu, 27 Apr 2017 11:47:41 -0700 (PDT), Dupéron Georges wrote: > If I understand correctly, [...] Yes, that all looks right. > It would be nice to find a way to detect what code gets executed when > a module is required, at the various meta-levels. Maybe running raco > cover on an empty file

Re: [racket-users] How to improve compile times?

2017-04-28 Thread Dupéron Georges
> > * Alex Harsanyi's start-up time is due to run-time (phase 0) initialisation > > code in the required libraries, including things like (define v > > costly-expression), which look like they could be saved as constants, but > > actually involve running the expression. > > I actively try to

Re: [racket-users] How to improve compile times?

2017-04-28 Thread Alex Harsanyi
On Friday, April 28, 2017 at 2:47:41 AM UTC+8, Dupéron Georges wrote: > Thank you Matthew for the explanation. > > If I understand correctly, > > * Alex Harsanyi's start-up time is due to run-time (phase 0) initialisation > code in the required libraries, including things like (define v >

Re: [racket-users] How to improve compile times?

2017-04-27 Thread Dupéron Georges
Thank you Matthew for the explanation. If I understand correctly, * Alex Harsanyi's start-up time is due to run-time (phase 0) initialisation code in the required libraries, including things like (define v costly-expression), which look like they could be saved as constants, but actually

Re: [racket-users] How to improve compile times?

2017-04-27 Thread Matthew Flatt
At Wed, 26 Apr 2017 15:04:15 -0700 (PDT), Dupéron Georges wrote: > However, I'm not sure what operations can cause compile-time code to > be run in this situation. My (possibly incorrect) understanding is > that macros are executed only once (when expanding the code), but the > code to the