want to add encoding as well? about wuffs HOT 3 OPEN

Another motivating example for this: I just implemented pieces of BGP in Go for a project of mine. Since I'm speaking BGP to someone else, I need both parsing and serialization.

BGP is not the world's hardest protocol to parse. It's mostly basic types and TLV-encoded arrays. However, it's evolved over 20 years and a dozen or more RFCs, and as such has picked up a number of subtleties that tripped me up while implementing. Fuzz testing was very helpful, but there's a limited corpus of BGP pcaps out there, so I don't have much faith that my fuzzer is covering useful ground.

This seems like a good use case for puffs, but parsing alone is not that useful.

from wuffs.

Yes, I absolutely want to support encoding eventually, and e.g. encoding JPEGs and PNGs are already in the doc/roadmap.md file. It just hasn't been the highest priority thing to work on so far.

Sorry if the "Parsing" name suggested otherwise. In any case, I'm probably going to change the name: https://groups.google.com/d/topic/puffslang/cSrH-s7UqwA/discussion

from wuffs.

If I get to learn how I will soon

from wuffs.