Christoph Wille

I have to read up on WebCil again but I think I saw that no header was one of the features.

There was no joke at all.

Do you need any of those? We picked what we considered "most common", and intentionally did not go for everything.

"Just because" is not a justification. I specifically asked which ones you think are missing.

Via #2869 ilspycmd could now use settings classes.

I said could, not is. ILSpyX is a shared library of classes that used to be in ILSpy (now split out for reuse in other Frontends) And, yes https://github.com/icsharpcode/ILSpy/blob/master/ICSharpCode.ILSpyX/PackageReadme.md is...

I don't know how that applies to the Wasm side of things, but I haven't looked at https://github.com/open-policy-agent/npm-opa-wasm in a long time.

That is quite the upgrade leap; maybe you can take my perf test project https://github.com/christophwille/dotnet-opa-wasm/tree/master/src/Opa.Wasm.Benchmarks and repurpose it for memory consumption tracking?

https://github.com/christophwille/dotnet-opa-wasm/blob/a0a1da3211842370fa99a419b3c5b6ff27406613/src/Opa.Wasm/OpaPolicy.cs#L313 That calls into LoadJson https://github.com/christophwille/dotnet-opa-wasm/blob/a0a1da3211842370fa99a419b3c5b6ff27406613/src/Opa.Wasm/OpaPolicy.cs#L326-L338 So looks the parsing error actually occurs inside OPA.

https://github.com/open-policy-agent/npm-opa-wasm/blob/39950c934a9b739f86aabc9215d7c05809aa0443/src/opa.js#L37 https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/TextEncoder "The TextEncoder() constructor returns a newly created [TextEncoder](https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder) object that will generate a byte stream with UTF-8 encoding." ok, UTF-8 is what is used by the default JS...