Phillip Schanely

> And yeah, the length thing makes sense as an implementation limitation. I guess doing a union of lengths just has too much overhead? Most of the meaningful decisions in...

> > This is a good point. Thinking about it again, I think the ideal interface would be something where I could give ancillary context managers for wherever you manipulate...

@Zac-HD crosshair is finally on the latest z3! I think we may also need some sort of issue for figuring out what to do with settings; I think crosshair too...

> Instead of more interaction between settings, can we just add those to the example configuration? Yup, I think that's fine, especially as we're getting started.

> [@pschanely](https://github.com/pschanely) you may also want to investigate the `Why.undiscovered` tests, marked mostly in [755486a](https://github.com/HypothesisWorks/hypothesis/commit/755486ab9ea6a5c56962f20474b92201714a489d) - it's a collection of cases where Hypothesis' heuristics find a failing example, but Crosshair...

At least right now, CrossHair isn't amazing at string parsing tasks like this, but with native crosshair (and some expansion of default timeouts), it'll work; you should get a counterexample...

> Note also that, even without identity intercepts, we could be doing this when the values are of a uniform type and representable with symbolics. As of [v0.0.86](https://crosshair.readthedocs.io/en/latest/changelog.html#version-0-0-86), this portion...

@Zac-HD Done with one round of investigations and fixes! (hypothesis-crosshair 0.0.13 and crosshair-tool 0.0.68) Breaking up the tests into categories: `minimize()` tests - should we never be running these with...

> That skip is specific to running `minimal(...)` _inside `@given()`, i.e. instead of crashing with the nested-tests error we just skip that test. On investigation there's a very obvious guess...

I got sidetracked on a few subtle-but-important issues this week, but this is still a big priority! I'll be looking at these in the next few days.