Great to see it! I haven't had time to review the code, but in regards to module naming: if the APIs in CodableStructuredHeaders are intended to be the primary surface for the library, shouldn't that module get the nicer name? Perhaps the current StructuredHeaders could be LowLevelStructuredHeaders or something less verbose but still indicative of its intended use. That way using the obvious name, StructuredHeaders, would give users the functionality they expect.
3 Likes