Apply the StringSegment treatment

[sebastienros]

From the benchmarks I have done for the library where I am using Irony, I can say that it's allocating a lot of memory. I think that modifying the code base to use StringSegment would improve things a lot.

It might not be an easy change but would probably improve the overall performance. I might try to do it when I find the time.

[daxnet]

@sebastienros , Looks interesting. Please just go ahead. And the situation from my side is the same: do not have enough time during these days. ;(
Thanks for your effort. And by the way, I have some questions in defining my own LOGO programming language with Irony, if possible, could you please help?

[sebastienros]

As far as I am knowledgeable, for sure.

[daxnet]

@sebastienros
Thank you!

Actually the grammar is defined here, which is not very complex, but when I open the compiled assembly by using the Irony Explorer, it shows me a Shift-Reduce conflict warning message. However when I use this grammar to do some parsing tests, everything works fine, I only see the warning in the Irony Explorer.

I know that it is because the ambiguous definition between the PARENTHESIS_EXPRESSION and the LPS + FUNCTION_ARGS + RPS portion in the FUNCTION_CALL definition that represents the function arguments, but I don't know how to eliminate this warning message. Do you have a good solution on that?

Appreciate your help!