Evaluate using StrategoTerms instead of ATerms in JSGLR
ATerm-based parse table loading is quite slow. Creating ATerm parse trees may be more expensive, if you’re just gonna throw them away. Converting ATerm parse trees to StrategoTerm parse trees in STRJ also is also quite slow (but maintains some of the sharing). Maybe we should just use (non-maximally shared) StrategoTerms in JSGLR?
Submitted by Lennart Kats on 16 February 2010 at 16:01
Issue Log
On 8 January 2013 at 16:05 Eelco Visser removed tag @lennartkats
On 8 January 2013 at 16:05 Eelco Visser tagged sdf
On 1 February 2013 at 10:53 Guido Wachsmuth tagged @maartje
On 1 February 2013 at 10:53 Guido Wachsmuth tagged 1.2
On 13 March 2014 at 08:53 Eelco Visser removed tag 1.2
Log in to post comments