Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

strategy_for_instances will behave arbitrarily with diamond inheritance #25

Closed
DRMacIver opened this issue Jan 16, 2015 · 1 comment
Closed

strategy_for_instances will behave arbitrarily with diamond inheritance #25

DRMacIver opened this issue Jan 16, 2015 · 1 comment

Comments

@DRMacIver
Copy link
Member

Suppose you have types A, B with instance definitions for both, and C subtyping both A and B. An instance of C will basically get an arbitrary strategy - it'll be stable across runs within a single process because of dict iteration order but will change from process to process.

Really this needs to be an error condition. If you have diamond inheritance you need to provide a more specific implementation for the more specific type.
@DRMacIver
Copy link
Member Author

Fixed in v0.4.1. This isn't an error condition, things are resolved in the defined python MRO.

DRMacIver added a commit that referenced this issue May 12, 2018
@DRMacIver
Merge pull request #25 from HypothesisWorks/DRMacIver/hashes
c88a2db 
Add providers for hashes
Macavirus pushed a commit to Macavirus/hypothesis that referenced this issue May 2, 2022
@DRMacIver
Merge pull request HypothesisWorks#25 from alexwlchan/continuous-rele…
aaf4a50 
…ases

Write about our continuous release process
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DRMacIver