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

I tried my minimal example and saw that this example only goes out of memory
in Wnadbox but compiles fine on my local machine.
In my project, I have a more complex Operand variant, and also a more
complex operator hierachy,
I am currently failing to break the problem down to one .cpp file.
I could upload my project to github if anyone wanna have a look.
The main problem was when I was adding

    auto const idx = as<ast::Operation>(helper::idxaccess_op > expression >
']');
    auto const func = as<ast::Operation>(helper::func_call_op >
expression%',' > ')');
    auto const data = as<ast::Operation>(helper::access_op > expression);

    auto const func_call_expr_def =
        primary_expr >> *(idx|func|data);

I am sorry for failing to break this down currently but I will do my best
tomorrow



--
View this message in context: http://boost.2283326.n4.nabble.com/Horrible-compiletimes-and-memory-usage-while-compiling-a-parser-with-X3-tp4689104p4689542.html
Sent from the spirit-general mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi