Re: Horrible compiletimes and memory usage while compiling a parser with X3
Seth <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
On 25-10-16 23:52, Exagon wrote: > I am sorry I wasn't able to minimize the code more than my example. > The approach of creating an custom parser with a parse function which calls > a non template parse function works well for me in this example. Oh, I didn't think your sample was too large! I was merely pointing out that there appears to be a real design issue with X3. The library was intended to resolve compilation time issues of Qi, not exarcabate them. And I posted that simpler case because it will be easier to use in spotting the things that give compilers a hard time. Whether or not you have a workaround, my feeling is this might need to be addressed in X3. Cheers, Seth ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik