Mathew Polzin

Right now you've got some build failures in the compiler where you've added functions to Data.String that were previously added to the compiler's internal Libraries.Data.String.Extra. We can't remove the definitions...

I'm immediately thinking the circumstance is different here and the compiler should I think complain if you try to hide the version you're adding now before it's available in the...

One thing to note: not all packages have main files and not all modules are guaranteed to be referenced by a package’s main file. This seems like a beneficial change,...

there's a duality of operations on fields when grouping that I think is at the crux of making it hard to represent type-safely. Setting aside syntax for a moment, just...

NOTE this should be done after pretty much every other v3.x task because all other OpenAPI 3.1 changes will impact the conversion between OpenAPI versions.

NOTE this should be done after pretty much every other v3.x task because all other OpenAPI 3.1 changes will impact the conversion between OpenAPI versions.

This might be workable by just defaulting to a more lenient decoding operation and adding the same guarantees back via the validation system so that decoding will succeed but validation...

This is a really cool idea for previewing inside Xcode! Who knows, maybe it could even graduate to a full WASM based web UI in the future! I also don't...

What it looks like is happening here is actually that Swift is quietly picking the variadic version of the `.string()` function and interpreting your array of strings as a single...

This became less urgent since I made resolution (now named "simplification") of JSON Schemas an optional step instead of part of dereferencing.