Tagging subscribers to this area: @dotnet/area-system-memory
See info in area-owners.md if you want to be subscribed.

Thanks for the issue and fix.

I'm not sure we should take this, though. It's been this way for a very long time, and there could easily be code relying on both casings being parsed.

Can you elaborate on in what situation it's breaking you that TryParse allows for additional casings to be parsed successfully?

Thank you for your feedback.

To be honest, I don't have a scenario in mind and I saw the "issue" when reading the code. I'm fine with keeping the current implementation, which allows parsing regardless of the case sensitivity.

Thanks. Personally, I'd be more inclined to "fix" the comment in the source as well as the docs, to make them match the long-standing behavior. But I'll leave that up to the area owners. @dotnet/area-system-buffers ?

I'd like weigh in from @GrabYourPitchforks since he was involved in getting this all supported in the first place.

I think this is overall less important if we just update System.Boolean to implement IUtf8SpanParsable and `IUtf8SpanFormattable. There are a number of existing quirks/oddities with the Utf8Parser/Utf8Formatter types and we opted not to "fix" those either.

Closing in favor of #103861.