Don Syme
Don Syme
This issue goes to the heart of differences in traditions in computing. In the algebraic tradition, adding data to a type is multiplicative, and nothing is "one" or "unit". So...
https://github.com/gregoryyoung/nothing/issues/7#issuecomment-660315947
[Hawking radiation](https://en.wikipedia.org/wiki/Hawking_radiation) seems relevant here
I see a big future for Nothing as a service.
The proposed fix (also the one adding "sealed") means we can no longer inherit from Nothing. It seems clear that each and every thing "is a" nothing - maximum flexibility...
Yes, this is needed, obviously. It's a shame the original designers didn't consider this direction when they got started. I suggest we also constrain `T` to be the underlying representation...
This type also supports the null value, see #2 . Please solve the programming language problem mentioned in that bug before adding further designs
> As described below the most significant complaint is that you can't use F# primitive operators like (+) on numpy arrays without an error. The workaround is to use the...
> The server-side diffing sounds related to what @krauthaufen and @dsyme are investigating with https://github.com/fsprojects/FSharp.Data.Adaptive This approach allows end-to-end diffing through a programming model (it probably also allows carving off...
I'm happy to get involved but my knowledge of E4000 consists of hearing one talk from Miguel and reading the docs for 10 minutes.... :)