Phillip Schanely

0.0.70 fixes that ugly regression with unhashables! The following two issues are going to take me a while, but, honestly, might legitimately be the next things to look at. >...

> Hypothesis now tests against Crosshair in our own CI runs, which will catch breaking changes on the Hypothesis side before we merge the PR, and on the Crosshair side...

Some of the support we need was implemented in #293, but there is still plenty of binascii left to implement.

Oh wow. OOC, from a product perspective, what does hypothesis do about this? `st.integers` is by default unbounded, and stringification is common (logging etc). But most users probably don't care...

@Zac-HD your triage above is SO great. I am investigating.

Knocked out a few of these in [0.0.60](https://pypi.org/project/crosshair-tool/0.0.60/). I think that means current status on my end is: - [ ] TypeError: conversion from SymbolicInt to Decimal is not supported...

Still here and excited about this! I am on a detour of doing a real symbolic implementation of the `decimal` module - should get that out this weekend.

> Got a good traceback for the `RecursionError` under crosshair 0.0.61: > I don't know what the respective `subclass, superclass` is but that sure seems like it could do with...

> I think the regex-related stuff and `LazyIntSymbolicStr` are probably the next-highest impact things to fix. OK! I'm hoping plugin version 0.0.9 will fix most of the LazyIntSymbolicStr errors. Can...

> @pschanely I'm overall seeing fewer failing tests (🎉🎉🎉), but also [this run just segfaulted](https://github.com/HypothesisWorks/hypothesis/actions/runs/10033844052/job/27727563015?pr=4034) maybe in `_crosshair_tracers`. Heh. I'm reasonably confident that CrossHair is not thread safe. This also...