Phillip Carter

Nice, I like it! If you'd like a final review, feel free to pull this out of a draft.

sure thing! Lemme patch that up. Thanks again!

I would agree with that change.

Setting aside the name for a moment -- do we feel that this accomplishes the goal of making it easy to create auto-closing spans as an end-user? If so, then...

Assuming names are agreed upon and look good, what all else would be needed to get this accepted and merged?

FWIW I believe that should that spec PR get merged, this is still considered valid as per spec: > Language SIGs MAY provide methods other than End in the API...

So this one is kinda funky. F# functions _emit_ as methods, so it's [technically correct](https://sharplab.io/#v2:DYLgZgzgPg9gDgUwHYAIDKBPCAXBBbAWAChiBtAHgEFtsAnASwCMBXXAVQgEMBzBACmp0mrBABVOtXtggA6ALIJsACxgATAJQA+ALrFsGRCgXK1AeSTAMghi1x91KALwpiKN2/pIlCBtnRZcPBlrYTt1YjJyYxVVc0sdYmBFFE5GAGMUeydXdxQAIlS0vKA=) that you can use `MethodOnly` on an F# function. However, in F# semantics there is...

I agree with @Rickasaurus here: > I rather like being able to inspect variables interactively in FSI. This is functionality I use regularly. It would be pretty annoying to have...

Another angle to consider is that active use of the REPL is common in other functional languages that we may wish to attract people from. Being able to say, "We...

There are several options to do this, the most immediately doable is to depend on [`InteractiveWorkspace`](https://sourceroslyn.io/#Microsoft.CodeAnalysis.EditorFeatures/Implementation/Interactive/InteractiveWorkspace.cs,7db98716da6643df) (requires a new shim in Roslyn to expose to F#) and plug in the...