Richard and Hongbo, I'm relieved to know that others are aware of the long compilation times = linking times for big projects and that it will likely get fixed in the next several months. I'm not going to worry about it in that case, and Hongbo's information on how little time it can take as OCaml does it is comforting, as there then is no reason that Even can't come up with something similar. I'll just look into if I can help on the speed of the generated code from the back end, which is something for which I may be able to help, and which Even doesn't have time to look into currently. It may turn out to be too much for me, but at least I'll know.
On Monday, 16 January 2017 10:21:28 UTC+7, Richard Feldman wrote: > > you need recompile that module and regenerate a monolithic js file, the >> larger project it gets , the worse compilation time you get in elm mode. If >> you have experience in C++, you know the bottle neck used to be linking, it >> is quite common for a c++ project to spend 20minutes in linking. > > > Considering Evan is working on asset management for the next release, I > doubt "compile everything to one file" will be true after it lands. (That > release is presumably still several months away; this is just speculation > on my part.) > > Evan also wrote C++ at Google, so avoiding long linking times is > definitely on his radar. ;) > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
