Skip to content

Conversation

@AlexeyRaga
Copy link
Collaborator

I was looking at #451 to understand why it happens.

Turns out it happens because PropertyArgs.init is a value, and not a funciton.
Which means that it does start with the random seed, but all the properties in a run use the same random seed.

This causes different properties generating the same values.

@moodmosaic I am not sure if it is a bug or a feature. From my PoV it is a bug :)
If you agree, here is the fix.

@AlexeyRaga AlexeyRaga requested a review from moodmosaic December 3, 2025 05:45
Copy link
Member

@moodmosaic moodmosaic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! The bug was caused by sharing a single, memoized initial state across all properties. Instead, every property check should get a fresh, unique initial state (which is what this PR fixes). Thank you!

@AlexeyRaga AlexeyRaga merged commit 5cca871 into master Dec 3, 2025
3 of 4 checks passed
@AlexeyRaga AlexeyRaga deleted the start-with-random-seed branch December 3, 2025 22:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants