Make BoxPredicate::find_case use the inner find_case

[rynoV]

So that test failures still show nicely when using boxing. For example this is the failing test case output:

  left: "Case { predicate: \"Some(var > 5)\", result: false, products: [(\"var\", 4)], children: [] }"
 right: "Case { predicate: \"Some(var > 5)\", result: false, products: [], children: [] }"

Showing that previously the debug information was missing when using find_case

[epage]

So that test failures still show nicely when using boxing. For example this is the failing test case output:

  left: "Case { predicate: \"Some(var > 5)\", result: false, products: [(\"var\", 4)], children: [] }"
 right: "Case { predicate: \"Some(var > 5)\", result: false, products: [], children: [] }"

Showing that previously the debug information was missing when using find_case

Note that we generally ask for tests to be added in a commit before a fix, showing the existing behavior. This would make the commit with the fix show how behavior changed.

[coveralls]

Pull Request Test Coverage Report for Build 21614236997

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+7.6%) to 15.331%

---

Files with Coverage Reduction	New Missed Lines	%
src/boxed.rs	1	43.75%

Totals
Change from base Build 21554052073:	7.6%
Covered Lines:	109
Relevant Lines:	711

---

💛 - Coveralls

[rynoV]

Thanks, re-ordered the commits and merged in master

[epage]

We actually ask that there be no merge commits and recommend rebasing

[rynoV]

done

[epage]

Does this test pass without the change?'

Every commit should pass tests