Jan Kotas
Jan Kotas
Crash under `JIT_Patchpoint`
> There's no trimming issues with DllImport that LibraryImport would fix. DllImports are trim-safe and in cases when they're not, LibraryImport doesn't help (things like AsAny marshalling that LibraryImport doesn't...
There is difference between "supported" and "probably works". We can only support .NET on supported OSes. > 10.15 is the minimum macOS version supported for .NET 8 According to https://en.wikipedia.org/wiki/MacOS_Catalina,...
> MAUI does declare a min supported version of 11.0 in our templates currently, Do you test MAUI on this min supported version?
AssemblyLoadContext or AppDomains give you a semblance of isolation. They do not protect you from process global side-effects. Benchmark authors would still need to be careful about the process global...
There is a ton of global state throughout the runtime and runtime libraries that is not isolated by AssemblyLoadContext or AppDomains. One example from many: Benchmark calls `GC.AddMemoryPressure` without removing...
Unity editor uses AppDomains for assembly load context isolation to allow reloading the user code. AppDomains do not provided strong isolation from side-effects with perf impact. They may isolate from...
The perf tests for libraries like that can clear the pools using private reflection or using the new .NET 8 [UnsafeAccessor](https://github.com/dotnet/runtime/issues/81741) feature.
More context: https://github.com/dotnet/runtime/issues/98426