You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since .NET Core dropped support for the serialization of System.Text.Decoder instances, the current serialization-based approach for supporting any Encoding on large input streams seems no longer viable.
A programatic way forward would be to only support UTF-(8|16|32) encodings and then do the decoding state management ourselves. This would also allow us to get rid of Cloning.cs. (Side note: the time I put ~15 years ago into making the serialization-based approach work and performant was completely insane.)
The text was updated successfully, but these errors were encountered:
Since .NET Core dropped support for the serialization of System.Text.Decoder instances, the current serialization-based approach for supporting any
Encoding
on large input streams seems no longer viable.A programatic way forward would be to only support UTF-(8|16|32) encodings and then do the decoding state management ourselves. This would also allow us to get rid of Cloning.cs. (Side note: the time I put ~15 years ago into making the serialization-based approach work and performant was completely insane.)
The text was updated successfully, but these errors were encountered: