-
```
It would be useful to match an annotation on the class, this comes in handy
when intercepting the constructor (see issue #163) and finalize method (see
issue #164).
This would allow a single anno…
-
```
Should be ? super T not ? extends T.
```
Original issue reported on code.google.com by `nat.pr...@gmail.com` on 14 Oct 2009 at 8:26
-
```
We need a matcher to do bitwise comparison. This is useful for validating
binary data or POD types that don't have operator== defined. For example,
BitEq(x) -- the value equals x bitwise.
…
-
Tests should be added for the cases in which the result is a failure, but doesn't match the specified domain or description.
-
```
We need a matcher to do bitwise comparison. This is useful for validating
binary data or POD types that don't have operator== defined. For example,
BitEq(x) -- the value equals x bitwise.
…
-
```
We need a matcher to do bitwise comparison. This is useful for validating
binary data or POD types that don't have operator== defined. For example,
BitEq(x) -- the value equals x bitwise.
…
-
```
It would be convenient to have a new any_args() matcher that would catch *all*
calls to a method, no matter which arguments it used.
So this code:
when(MyClass).my_function(any(), any(), any()…
-
The changes proposed in https://github.com/SchibstedSpain/Barista/pull/223 raised the discussion of just having simple methods for searching views by id and text, or having more combinations for speci…
-
The result of myzod causes Jest's `.toEqual`'s skipping of undefined keys to not work. I am assuming this is due to some prototype hacking?
i.e.
```
expect({a: undefined}).toEqual({}) // pass
…
-
since this works:
```
(matcher-combinators.standalone/match?
{:a matcher-combinators.matchers/absent}
{:c 'd})
;; => true
```
I would expect that
```
(matcher-combinators.standalone/match?
…