Escape characters in diffable cs field default values

[ItsMilos]

System.Globalization.CharUnicodeInfo is supposed to look like this:

public static class CharUnicodeInfo
{
internal const char HIGH_SURROGATE_START = '\ud800';
internal const char HIGH_SURROGATE_END = '\udbff';
internal const char LOW_SURROGATE_START = '\udc00';
internal const char LOW_SURROGATE_END = '\udfff';

and in DiffableCsOutputFormat.cs line 184 those default values are characters, not strings

if (defaultValue is string stringDefaultValue)
sb.Append('"').Append(stringDefaultValue).Append('"');
else
sb.Append(defaultValue); // it tries to do this, but it cant be encoded

public static class CharUnicodeInfo
{
internal const char HIGH_SURROGATE_START = �;
internal const char HIGH_SURROGATE_END = �;
internal const char LOW_SURROGATE_START = �;
internal const char LOW_SURROGATE_END = �;

Unhandled exception. System.Text.EncoderFallbackException: Unable to translate Unicode character \uD800 at index 119 to specified code page.
at System.Text.EncoderExceptionFallbackBuffer.Fallback(Char charUnknown, Int32 index)
at System.Text.Encoding.GetBytesWithFallback(ReadOnlySpan1 chars, Int32 originalCharsLength, Span1 bytes, Int32 originalBytesLength, EncoderNLS encoder, Boolean throwForDestinationOverflow)
at System.Text.Encoding.GetBytesWithFallback(Char* pOriginalChars, Int32 originalCharCount, Byte* pOriginalBytes, Int32 originalByteCount, Int32 charsConsumedSoFar, Int32 bytesWrittenSoFar, EncoderNLS encoder)
at System.IO.File.WriteToFile(String path, FileMode mode, ReadOnlySpan`1 contents, Encoding encoding)
at System.IO.File.WriteAllText(String path, String contents)
at Cpp2IL.Core.OutputFormats.DiffableCsOutputFormat.DoOutput(ApplicationAnalysisContext context, String outputRoot) in Cpp2IL.Core\OutputFormats\DiffableCsOutputFormat.cs:line 46
at Cpp2IL.Program.MainWithArgs(Cpp2IlRuntimeArgs runtimeArgs) in Cpp2IL\Program.cs:line 613
at Cpp2IL.Program.Main(String[] args) in Cpp2IL\Program.cs:line 531

[ds5678]

This feels like a hack. Ideally, your pr would fix the underlying issue.

How about you post the stack trace you encountered and information about how it can be reproduced.