Another possible fix would be to add public extensions of Array, Set, and Dictionary such that they can also use == or != with Optionals. I elected not to do that because I'd rather not change the behavior of these very common types just for Nimble. It felt way less riskier to bring back these matchers.
Maybe in the future, Swift will be enhanced again so that we can actually simplify these matchers.
This extends and solves https://github.com/Quick/Nimble/pull/962 by doing what @ikesyo suggests as the fix.
Another possible fix would be to add public extensions of Array, Set, and Dictionary such that they can also use
==or!=with Optionals. I elected not to do that because I'd rather not change the behavior of these very common types just for Nimble. It felt way less riskier to bring back these matchers.Maybe in the future, Swift will be enhanced again so that we can actually simplify these matchers.
Thanks @acecilia for bringing up this issue!