Jan Kotas

> The current thought will be to leverage TypedReference and have developers supply callbacks The idea behind this is to build a better interpreter than System.Linq.Expressions. It may make things...

The default for the WinRT (store) apps should be the constrained environment, where the transitive closure of all types is known, without reflection fallbacks. Otherwise, the WinRT apps are going...

> Here's the API I'm thinking of It would be nice if this API allows hydrating the registrations lazily. E.g. If the app has 1000 types but only one of...

> Is ty.GetCustomAttributes(typeof, false) etc. used in FSharp.Core considered "reflection-free" for the purposes of trimming, Reading custom attributes is compatible with trimming and AOT compilation. (I would not call it...

> it's probably a codegen issue. Yes, this looks like a codegen issue or GC heap corruption. It does not look like a real OOM.

It is most likely a bug in the .NET runtime port to LA64. It is unlikely to be a bug in the F# compiler itself.

> Relax the rule on ref-structs as fields to allow them as static-readonly fields. Though need runtime/gc people to state if that will be a problem or not. Yes, that's...

> Can we relax this in some fashion? `static` fields are stored on the GC heap just like anything else. This is hard trade-off for the runtime to make. If...

The `byref` in `Span`/`ReadOnlySpan` are expensive for the GC to walk. The GC has to find the containing object for them that is an expensive operation.

So that it can mark the object as reachable.