Phillip Carter

Labeling as a bug due to the internal error - whether or not this should actually compile is a separate question, but from a usability standpoint the internal error needs...

Severity is probably sort of low, but it is not done. There is a terrible dependency chain that involved this tragedy: https://github.com/dotnet/fsharp/blob/main/vsintegration/src/FSharp.ProjectSystem.Base/Project/ProjectSystem.Base.csproj#L74 I filed this because I was looking to...

FWIW I think this is probably more the domain of telemetry backends than OTel itself. I'm aware of at least one (service now observability, formerly lightstep) that has robust critical...

For non-async traces, critical paths are pretty easy to calculate (just walk backwards!) but yes, because there's nothing between peer spans saying that they're peers, you need to "draw" the...

Yeah, the way most critical path systems work is they work backwards from the end of the trace and (sometimes via recursion) figure out what's most blocking. Uber has a...

Closing out old PR -- I realize we wanted to say something here but it's been a few months, so feel free to re-open if you think it's still worth...


@dsyme @TIHan the issue here is that `nameof` in either case is not actually in the captured name resolutions. For both of these examples: ```fsharp type C let rec f...

@dsyme I bumped this out of low priority. Colors have significance in the editor and by not being accurate here we're effectively misleading folks. I suspect this will get a...

This may be a current limitation in the language, actually. We don't really have a good way to declare these things in F# code today. We can probably still get...