Tomas Grosup

Anything below 20 minutes is fine - I hope copies are not needed. We can also have multiple entries (e.g. cloning the same repo, but running a different script ).

> Also, if we add `ofNullable` (and decide what to do for null), then surely we should also add `ofOption` with similar semantics. > > There's also the `ofObj` /...

A side-thought if this is an existing common concern - expensive read-only properties on records could likely be solved via an `static let ConditionalWeakTable` and the boilerplate probably even generated...

Having another round of thinking, it would be difficult to make such "empowered" records work on older versions of the compiler - signature data and optimization data might not be...

F# is a language that interops - be it with rest of .NET, or via Fable. That means that some effects will always stay hidden behind function calls, and bypass...

> Perhaps polymorphic variants would provide a way out? You are right, you would need to define another discriminated union as a choice over the effects you want to use...

I do like the additional safety and robustness (against "code somewhere above changes") this brings. At the same time, it is another of those "two ways for doing the same...

@IS4Code : What if you could have a warning that triggers every time an equality expression in method arguments without explicit parens (`x = 1`) shadows a settable property/parameter symbol...

The semantics would be that `~symbol` can only ever resolve to a function/method parameter name, and name resolution would prevent from resolving it to any other scope?

So `f (~x = 1, ~y=false)` can either: - Call function with two parameters `x` and `y` - Call function `f` with a single tupled parameters, which is a named...