Jan Kotas
Jan Kotas
> we move the ASP.NET relevant bits from 2.1 Where are we moving the ASP.NET relevant bits from 2.1? I am wondering whether we need to have dotnet/runtime-graveyard repo for...
Have you looked at the CI failures and determined that they are unrelated? This is same type of change as https://github.com/dotnet/corefx/pull/42900. It is fine to take it. It should follow...
> Better experience for runtime.json style packages. Isn't runtime.json the metadata you are looking for? The runtime.json packages are "packages with native dependencies". The "runtime" searches are just a tip...
> Currently there are only 5 uses of Environment.IsWindows8OrAbove in corelib. There are more than hundred places where we have workarounds for Windows 7 (most of them are in tests)....
Note that we are deleting the support for other OSes that are EOL too. For example, https://github.com/dotnet/runtime/issues/60138 .
Context: https://github.com/dotnet/runtime/pull/72082#issuecomment-1185706575
Mutating strings like this is a bad practice and not supported by .NET runtime. You should use string constructor that takes `ReadOnlySpan` to avoid the allocation here.
> That constructor doesn't exist on netstandard2.0 though, so one would then need an #if here. Yes, that's what we do in dotnet/runtime in situations like this.
> we might want to reconsider interop support for generic delegates or generic unmanaged function pointers If we had that, how would you create the generic instantiations? Would all generic...