-
Joined on
2023-07-06
Okay, I now understood your explanation from the other thread. I guess if the result parses with treesitter we should be relatively alright? Succesfully compiling real world examples will be hard…
Sorry, that’s not enough context for me. I would like to understand what is the problem with the currently existing Haskell tests, if that’s what’s going on.
When you need a way to…
Ah, sorry. I was still planning to write the tests, but I didn’t find the time. You can ofc. merge without I don’t think I could write a test which would find invalied merges introduced by…
The good news is that I couldn't implement that specific commutativity because the Haskell treesitter grammar is not suited to it. So no need to remove anything. 🥳
Thx! I am still amazed by how ergonomic this was. Looking forward to the next release.
Sadly it is more complicated than that. We could have
<<<<<<< LEFT
import Foo(foo,Bar(baz))
Sadly I have struggle adding the other features:
Lets look at deriving:
│ └deriving: deriving
│ ├deriving
│ └classes: tuple
│ ├(
│ …
All excellent ideas. Especially the type class constraints actually frequently produce merge errors in our codebase.
I will try to get to it quickly but imo this PR is self contained and doing…