Skip to content

Fix Content::walk not being recursive#80

Merged
mitsuhiko merged 1 commit intomitsuhiko:masterfrom
LPGhatguy:fix-content-walk
Oct 20, 2019
Merged

Fix Content::walk not being recursive#80
mitsuhiko merged 1 commit intomitsuhiko:masterfrom
LPGhatguy:fix-content-walk

Conversation

@LPGhatguy
Copy link
Copy Markdown
Contributor

Content::walk claims to be recursive, but actually isn't! This caused the sort_maps feature to only affect maps at the top level, which is causing snapshot nondeterminism in one of my projects.

Additionally, three tuple-related variants were not present. I don't think I had these present in my projects, but it seems they were omitted by error.

I changed walk to accept the visit callback via a reference instead of by value like before, since now that reference needs to be passed through multiple calls to Self::walk and cannot be moved.

@mitsuhiko mitsuhiko merged commit 8e32e35 into mitsuhiko:master Oct 20, 2019
@LPGhatguy LPGhatguy deleted the fix-content-walk branch October 21, 2019 21:53
LPGhatguy added a commit to rojo-rbx/rojo that referenced this pull request Oct 21, 2019
Map sorting in Insta was previously not recursive.
As of this PR, it is!
mitsuhiko/insta#80

Since it hasn't made it into a release yet, but is
important for Rojo to have snapshot determinism,
we're moving temporarily to depend on Insta via Git.
Dekkonot pushed a commit to UpliftGames/rojo that referenced this pull request Jan 11, 2024
Map sorting in Insta was previously not recursive.
As of this PR, it is!
mitsuhiko/insta#80

Since it hasn't made it into a release yet, but is
important for Rojo to have snapshot determinism,
we're moving temporarily to depend on Insta via Git.
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.

2 participants