Tuning branch retains previous parse trees.

[postmodern]

I noticed that the results from previous parsing, stays within the parser object.

parser.logical_and_expression.parse('1 && 2')
 => {:binary_and=>{:left=>{:constant=>"1 "}, :right=>{:constant=>"2"}}} 
parser.logical_and_expression.parse('1 && 3')
 => {:binary_and=>{:left=>{:constant=>"1 "}, :right=>{:constant=>"2"}}} 

[kschiess]

I know. The tuning branch is kind of a development/hacking branch and as such only a preview on upcoming worlds of execution speed. It has certainly got serious issues (code quality is low for now), but this is the only real bug that I know of.

Fixing this requires a partial rewrite that I am undergoing right now. Please be patient; If you want working code, use the gem or master.

Alternatively, dont reuse your parsers for now, at least not with the tuning branch...

Apropos: I find it curious that we cannot indicate which branch a ticket is about except by writing it in the text...

[postmodern]

OK, will hold off until later.

You should make a Label for "tuning".

[postmodern]

Also, the performance on master / 1.0.x is so horrible, it makes parsing the most basic C expression take close to 1 minute. This lead me to test the tuning branch; which is incredibly fast!

[kschiess]

This has been fixed in the current HEAD of tuning. I have now a regression that prevents this from happening.