Phillip Schanely

Interesting. Indeed, this feels fairly distant from CrossHair's current implementation, as we don't really collect path conditions in any form other than SMT. There probably is space for the definition...

See also #165 for another use case that might benefit from work in this direction.

An update: there is now some (pretty experimental) stub parsing code in place. This is only used by [register_contract](https://github.com/pschanely/CrossHair/blob/4abaac436f383abf3bcc705a4a521d9cd824d4e5/crosshair/register_contract.py#L182) at the moment, but we could try using it for creating...

Thanks for the report! Looks like we're having trouble resolving some of the type annotations here. I'll investigate this week and get back to you.

Ok! So, I spent some time digging into SQLFluff + CrossHair: it's an interesting use case! Most immediately, I've fixed the NameError issue at head. (essentially, the "TemplatedFile" import was...

The original NameError issue should be fixed in [v.0.0.22](https://pypi.org/project/crosshair-tool/0.0.22/). Going to continue to leave this issue open, though, for additional SQLFluff discussion if we want it.

Love this idea. And it might not be all that difficult to do; the stuff we'd need to change is relatively well encapsulated in `get_fn_conditions` and `get_class_conditions` in [condition_parser.py](https://github.com/pschanely/CrossHair/blob/master/crosshair/condition_parser.py). There...

An update: at present we support: PEP316, icontract, deal, an assert-based mode, and hypothesis. See [these docs](https://crosshair.readthedocs.io/en/latest/kinds_of_contracts.html) for details.

Ascii, utf8, and latin-1 all have symbolic support for encode/decode in v.0.0.20! Reply below to vote for other encodings that would be helpful for you.

Ah. Yeah, I think in the abstract, I have a slightly contrarian preference about putting tests close to the code they test. BUT, particularly as CrossHair becomes a more distributed...