> > So out of pure curiosity - are there obvious optimizations in the linker > which are still pending? >
We have been thinking about strategies to incrementalize the work done by the linkers, one idea is to have a linker that outputs js for different Java classes to different resources and that could be incrementalized. > > For example, I noticed that a huge amount of time (> 50% of the whole > linking time) is spend in "Saving source with extras", i.e. SourceSaver. > Given that these sources are only needed by the browser during a > sourcemap-based debugging session, can't they be served on the fly by the > code server rather than being pregenerated on disk during the > recompilation? There are debugging scenarios (in-IDE debugging with SDBG), > where these source files are not even needed and never requested from the > codeserver. > > I am currently working on this one. There are two options here: 1) serving source code directly without copying and 2) copying only "changed" sources. Option 1) would be the optimal in terms of compile time but it might result of a worse debugging experience (if you modify a source while debugging the source mapping will be out of date). -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/cc62d937-5db6-451a-b2d5-65982dcc9f5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
