Phillip Carter

Aha, makes sense! Yeah, those shouldn't be hosted on the website. There may be some interesting future wherein we figure out a good way to represent language API reference docs...

I created https://github.com/open-telemetry/opentelemetry.io/issues/1808 based on discussion here. No pressing need to engage, but for now we do link to the API reference and will see if there's a way to...

@ringerc I think your issues may be best sorted out in the OTel docs, where there is a lot of what you mention here: https://opentelemetry.io/docs/instrumentation/js/instrumentation/ Happy to clarify more stuff...

I think we can probably consider this resolved, at least the major pain points, with the website docs (https://opentelemetry.io/docs/instrumentation/js/instrumentation/) getting an overhaul recently. Nearly all major concepts are now documented...

I moved back to .NET 6 for the action: https://github.com/SaturnFramework/Saturn/blob/main/.github/workflows/docs.yml#L19 Any concerns with merging and iterating from there?

@64J0 unfortunately no, I don't know much about this particular docs tool. As for FSharp.Formatting, yes, it's undergone an incredible amount of breaking changes as well. I almost wonder if...

I would +1 on awaiting the beta.

cc @NTaylorMullen - this is interesting, since the exception is coming from CoreFX

Yeah, if we broke compat with .NET Framework then we could do this I think. But that's a pretty big change to make, and although the majority of F# developers...

I think that given the reasoning above (both for FABLE and the use case @Horusiath mentioned), this would be a good addition. 👍