Greg Pfeil

This, like #4733 seems to have been fixed in the round-trip, but leaves some incorrect definitions in codebases. If I use the from-scratch examples in this issue or #3757, things...

I definitely think Unison shouldn’t do the same as Haskell does – a fixed set of levels, with operators hardcoded at various points. I’ve personally felt a lot of pain...

> Another option: > > 3. It's a parse error to mix operators in the same expression without parens. So `x + y * z` requires parens. `x + y...

> Any precedence rule that introduces a cycle given the rules that already exist in its dependencies is an error (this could cause an issue when you pull in two...

To mitigate my previous comments a bit – I’m in favor of the “hard-code PEMDAS, leave the remaining behavior as-is” approach. Would definitely be an immediate improvement.

Yeah, this confused me at first as well (especially since the docs don’t match the behavior). I _prefer_ Unison’s implementation of this, but also understand that users may be expecting...

GitHub is CommonMark + extensions, and I think leaning toward CommonMark is the way to go. 1. it’s the closest thing to a standard; and 2. it’s what we‘re using...

Here it is rendered in the UI: 

Oh, thanks for catching this! From the original issue, I thought the error was happening during typechecking (and maybe it had been?), so I figured even `ui` was just a...

Do we have any way to track “known failures” in `transcripts` or otherwise? This is different than “unexpected success”, as “unexpected success” are tests that are _supposed_ to fail, whereas...