unison
unison copied to clipboard
A friendly programming language from the future
I attempted to define: ``` structural type Functor f = {map : forall a b. (a -> b) -> f a -> f b } ``` Which failed with: ```...
From @ceedubs: When we complain about an ambiguous suffix, we should show the whole `very.long.name.wow.so.long`, not a suffixified `wow.so.long` (so that debugging the issue is easier). From @aryairani Can we...
Docs are parsed into Unison terms one-word-at-a-time, which means a doc with 2000 words has at LEAST 2000 function calls 🙃 . Even worse, the way it's resolved, it doesn't...
When we complain about an ambiguous suffix `foo` that could refer to `one.foo` or `two.foo`, we should always use names `one.foo` and `two.foo` (as opposed to an alias).
The expression `0.1 + 0.2` is unambiguous because TDNR uses the expected type of `+` to figure out that what's meant is `base.Float.+`. But when this gets pretty-printed out again,...
and even if it did, we don't have a syntax for "not a local variable" (e.g. if a reference is named `foo.bar.baz`, so we can call it one of `baz`,...
## Overview A place to notice pretty-printing changes. ## Implementation notes ## Interesting/controversial decisions * It takes a while to run, we may want to split them out into a...
**Describe and demonstrate the bug** If you omit a blank line before a triple-backtick code block, then it gets interpreted as a double-backtick inline code sample. I don't know Markdown...
``` test.laws.associativity.doc : Doc test.laws.associativity.doc = {{ Checks the associativity property of a binary operation. `` associativity gen f `` checks that for all elements `x`, `y`, and `z` returned...
When we hit an unexpected server response, summarize it with the status code, status message and the response body instead of dumping the raw Haskell data-structures. This fixes https://github.com/unisonweb/unison/issues/5341 though...