Luís Campos

I'll have a go at this one. ;)

Unfortunately, after having a look, it seems that this would take me more time than I'm willing to spend on it. :disappointed:

I'm looking into this ^^

`beSome` expects a function that returns a `MatchResult`, but when we use `and` we force specs2's `MatchResult` into weaver's `Expectations`. specs2 has its own `and` but it's overloaded by weaver's....

@Baccata, I would say that having a different a different test method (`spec(...)`) is undesirable from a user experience point of view. :confused: Although it might be the best option...