Re: Horrible compiletimes and memory usage while compiling a parser with X3

On 23-10-16 21:40, Exagon wrote:
> I tried to minimize the code arround the expression parser, but its somehow
> not that trivial. 

I've noticed similar issues with much simpler code:
https://stackoverflow.com/questions/37230653/compile-times-with-boost-spirit-x3/37242969#37242969

Quoting my own comments there

> @RichardHodges This timing though is certainly indicative of a
bug/implementation flaw. Usual X3 grammars this would compile in
seconds. I'd expect 10s maybe due to the other uses of variants
(|apply_visitor|) which are quite template heavy. But as you can see in
my answer, the situation is a lot more severe than this. – sehe
<https://stackoverflow.com/users/85371/sehe> May 15 at 19:52
<https://stackoverflow.com/questions/37230653/compile-times-with-boost-spirit-x3/37242969#comment62014796_37230653>


<https://stackoverflow.com/questions/37230653/compile-times-with-boost-spirit-x3/37242969#comment62014796_37230653>

Do any of our X3 buffs know what is going on?

I personally think it's instantiation depth in the face of aggressively
inlining compilers. (It's hard to decide what is the best approach. We
want inlining, but at what cost? Is there a good, library-defined,
cut-off point?)

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

_______________________________________________
Spirit-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spirit-general