Hello, I've got a package that generates (i.e., expands into) a ridiculous amount of Racket code. I'd like to generate an unbelievable amount of code, but things have already slowed down a lot.
At this point, I'm generating 20% of a massive code base and it takes 4 minutes to compile (i.e., raco make) it all. If those numbers scale linearly, I'm looking at 20 minutes to generate and compile the full code base. Realistically, that's an optimistic lower bound. How might I go about profiling something that does most of its work at expansion time? Should I be concerned about knocking over or clogging the package repository when checking in highly "compressed" meta-programs that unfurl at compile time? Thanks! Eric -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAORuSUwpmXpytBA1em6F1RZMkFGu1X9r88xWKqaMFrC%2BS1U7hw%40mail.gmail.com.
