Kevin Ransom

@saul ... could Roslyn make F# proxies work? After all these used to work, and so this is a breaking change. I think before we introduce a language change we...

I just found this in the compiler; ```` // Workaround for .NET and Visual Studio restriction w.r.t debugger type proxys // Mark internal constructors in internal classes as public. let...

@saul checkout this: https://github.com/Microsoft/visualfsharp/pull/2830 I tried it out on my machine, Even with a public setter the debug proxy didn't work. Any ideas?

@dsyme, our internal programming guidelines when I was in Windows working on WCF, was to declare the members of internal types with their '**natural**' visibility, I.e. the visibility you would...

@dsyme an rtm install of the dotnetsdk contains crossgened assmeblies. So they are always executed crossgened. For code built from the F# repo crossgen is not applied. The likely big...

My suspicion is that we pre-load a ton of assemblies before compilation. We only ship native compiled assemblies to the dotnet sdk, so that start up time is for native...

I would like to see more interop tests, - using C# Generic Attributes from F# - using F# Generic Attributes from C# and VB - I suppose VB supports them....

I think the goal of this would be to read the attributes of the method at the delegate target. I suppose the C# delegate equivalent of this would be .....

Harrumpph!!! VS2019 did the same: 

@dsyme we should create a backlog item for this. I particularly like the categorization of types, it's very helpful. I think though this applies to more than just F#, although...