Update mrbind to make the Python type registration order deterministic - #6545
Closed
Fedr wants to merge 3 commits into
Closed
Update mrbind to make the Python type registration order deterministic#6545Fedr wants to merge 3 commits into
Fedr wants to merge 3 commits into
Conversation
Fedr
marked this pull request as ready for review
August 7, 2026 19:54
Contributor
Author
|
Superseded by #6553 (identical gitlink bump to f2764c51), which is merged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Points
thirdparty/mrbindat current mrbind master (f2764c51), which contains the deterministic type registration order (236ba967) and deterministic alias ordering (f2764c51).This makes the
mrmeshpyregistration order — and with itmrmeshpy.pyi, the position of__init__overloads injected from conversion operators, and therefore overload resolution — reproducible across builds of identical source. Previously two same-source builds could differ: e.g. two independent master builds orderedAffineXf3f's conversion-injected constructors differently in the.pyi.Verified in mrbind by linking the same binding fragment objects in two different orders: the full
MRBIND_DEBUG=2registration dump is byte-identical (MeshInspector/mrbind#43 adds this as a regression check; it is test-only and not needed here).