Simon Vergauwen

I am running into this issue for all other native targets as well. Very strange though, when I move the same code to `macosX64Main` for example, then I don't run...

Hey @kierans, I only moved my test code to `macosX64Main`, and then build the binary and ran it. When I did that, then it didn't fail with the segment error....

> However moving test code into a main folder doesn't seem like a great solution to me. It's definitely not a solution 😅 It just shows that the segment error...

Hey @jakubgwozdz, This was sadly due to the fact that the tool we use to validate code completely broke over the `Validated` documentation when we upgraded. So we felt forced...

> is a song of distant future :) - I read somewhere else that you aim for Kotlin 1.9 or so... I think that was a miss-understanding. Arrow 2.0 is...

@Atternatt the error handling docs are IMO up for revamping after these changes. We’ve also changed how to do error handling in Effect, and I hope to change all APIs...

> I think the perfect alias would be Either, with some extension methods to create a Left with a singleton list. Is the idea to make everything work over `NonEmptyList`...

@Atternatt, we have a large number of conflicts 😱 Should we fix these first, and run the tests before reviewing?

@kyay10 removing OptionShift, NullableShift and ResultShift would be great but it seems context receivers will be out of scope for Arrow 2.0 since it’ll only become available in 1.9 or...

> However though, if we're having our minimal comparability be 1.7.x, could we still have context receiver functions in Arrow 2.0? (maybe in a separate package because I think turning...