matt rice
matt rice
This is mostly just for collecting feedback, as this patch is fairly incomplete, It implements the serialization stuff, and it adds a `-s` switch to nimbleparse to *output* the serialized...
Currently the [`parse_generictree`](https://docs.rs/lrpar/latest/lrpar/struct.RTParserBuilder.html#method.parse_generictree) function can be used to return a `Node` from there [`Node::pp`](https://docs.rs/lrpar/latest/lrpar/enum.Node.html#method.pp) can convert a parse tree, into a textual representation as used by `nimbleparse`. One thing I'm...
While I was considering looking into #417 it caught my eye that "{foo}" match the string `{foo}` literally rather than a substitution string. This one also goes under the banner...
Here is an attempt at getting it working on an older amd gpu. While it does work I do get a bunch of artifacts at the edges.
WASI
I only did a cursory search while running out the door, and saw some web assembly stuff, but didn't see WASI specifically mentioned which might be good to add above...
Something I avoided putting much thought into during the 0.14.0 development cycle. Currently the `%grmtools` directive is *very* conservative in the sense that the `CTBuilder`s and `nimbleparse` when they read...