Alejandro Serrano
Alejandro Serrano
The JS and Native builds are failing because they expect `arrow-continuations`, but this is in fact one of the things removed by this PR. ``` e: Could not find "io.arrow-kt:arrow-continuations"...
I guess I’ll have to revert the removal of the `test` modules, then.
Wouldn’t we have the same problem? We cannot depend on the test module until there’s a 2.x-compatible version, right?
Another option would be to stop depending on things like `ArrowFxSpec`, but keep the few utilities and generators in `commonTest` for each project.
@nomisRev @i-walker @raulraja this is now really ready to be merged, I've managed to remove the dependency on the tests on `main`, and take the whole thing up to here
This doesn't seem to be an issue anymore
> @JakeWharton Not that is probably matters but `summon` is what Scala 3 Type Class summoning uses. Indeed. Also it's uncommon enough to not be taken by any other framework...
Some answers and clarifications: - You never have to write `context context(A) fun ...` (in fact you can't), since `context(A)` is enough to mark the function as contextual. - Some...
Maybe this was not entirely clear from the document, but the contextual visibility only affects to context _receivers_, not named context parameters, which work like a regular parameter in terms...