Repository navigation
Fix remaining native portability compile errors - #644
Merged
Merged
Conversation
This was referenced Sep 19, 2026
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
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.
Closes #643 under #235.
Fix the two native portability compile errors unmasked after #642: construct the inclusive-descendant invalidation route in the valid/invalid pseudo branch that consumes it, and give the semantic support-bit lambda an explicit
uint32_treturn type.Captured failure: current-main CI
35432237355on Linux and macOS.Base:
2ec7f8530da8ab105a6499a4cd0a519d876a5a3bImplementation:
73ccdbced26191df94b4f906373fcbfb2c3ba42fValidation under the current throughput policy:
git diff --check.