Phillip Carter
Phillip Carter
FWIW I did notice this in gitpod as well several months ago, but I think it had to do with something on their end.
Just as a distinguishing note - we actually do ETW logging in the VisualFSharp codebase: https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/Logger.fs#L16 And that's fine. So it seems that there's a subtlety here where it goes...
I'm thinking we're also due for another rewording of this to clarify what resources are exactly. One thing I've noted seems to work well with people is framing it up...
I would say that if we did this, I wouldn't want a keyword. I'd much prefer it to be a scoping rule that "works" in top-down order: ```fsharp let doot...
Yes, it'd technically be a breaking change, but in ordering it'd be consistent with shadowing (most "recent" scope wins), so it's something I'd actually be in favor of introducing
Closing as completed by https://github.com/open-telemetry/opentelemetry.io/pull/5480
closing old PR
@michael2893 unfortunately one of your commits came from a different email not covered by the CLA. I'd recommend squashing that commit.
RIP tooling logic for handling dots 😄
It's very easy to implement this as a new `#r` directive, but rationalizing this with an F# scripting environment is pretty wild. Consider this script, where you execute it line-by...