Olivier Mélois

I'd also appreciate : * a test (though I don't mind if we defer, unless you want to take a stab at it). * an amendment to the documentation page...

The issue is that bloop is a compile **server**, and therefore the pwd is wherever bloop was started from. We need to find a workaround to access the "workdir" as...

@amumurst hi, and thanks for the contribution ! This feature had been requested by several people and was on my backlog, so the PR makes me happy. I'm gonna take...

I'm not sure I'd qualify this as a bug on weaver's side. Anything that plays with classloaders can be a little bit tricky when run through SBT in non-forked environments....

Okay. I'm afraid I'm gonna lack the time to dive into it and the actual expertise to pinpoint the problem without diving into it. I can offer a wild guess...

I have to admit I've never used the Discipline module in weaver myself. I'd be happy to undergo some changes to make this possible.

> What do we think? I'm not certain I want it, not certain I don't want it. @keynmol wdyt ? > Tangent Q: thoughts on a matcher for something like...

> exists does better It is correct that `forEach` is classically called `forall`. It is also worth noting that `exists` and `forall` are the exact dual of each other, folding...

You won't be able to write a generic `MonadError` integration, because all combinators would be working against the context of the `MonadError`, and does not give you the necessary abstraction...

`forSome` is a keyword in Scala 2, and also the `Some` suffix is tightly coupled to `Option` imho. How about `expectMatch` ?