Phillip Carter

@jwosty We should match what C# does here and lookfor the `GetPinnableReference` member. @tihan can be of help in figuring out how to determine that.

@TIHan not a draft anymore 🙂 https://github.com/fsharp/fslang-design/blob/master/RFCs/FS-1081-extend-fixed-expressions.md Design discussion here: https://github.com/fsharp/fslang-design/issues/421

I'm really undecided on this one. After programming a lot of haskell recently, I get the appeal. But something about it just doesn't feel right for an ML.

> Implement ToString() on F# function and other closure values so they do more than print the obscure closure name - as least add some indication the thing is a...

Just a note: > Small. It's a single keyword that's easily parsed and enforced. This is probably not accurate. This amounts to a new kind of access modifier, which is...

> Forcing users of my code to write `(x : PosFloat)` every time they want to access `Value` gets old quickly There are also two other things to consider: *...

I think I like this, since it's pretty confusing that you don't need to do `seq { x..y }` but you need to do `seq { x; y }`. Since...

I would personally support an off-by-default warning here.

See also: * #147 and [RFC for related attribute](https://github.com/fsharp/fslang-design/blob/master/RFCs/FS-1011-warn-on-recursive-without-tail-call.md) * Trial implementation by @aviavni: https://github.com/Microsoft/visualfsharp/pull/1976 @haf If you're interested, I think it would be productive to flesh out the existing...

Promoting the mutable value to a `ref` when it's closed over in an object expression like that is by design. Object expressions are objects that are allocated on the heap,...