fitzgen opened PR #12710 from fitzgen:range-iter-and-imm-cursor-for-bforest-map to bytecodealliance:main:
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
fitzgen requested cfallin for a review on PR #12710.
fitzgen requested wasmtime-compiler-reviewers for a review on PR #12710.
cfallin submitted PR review:
LGTM modulo one question below -- thanks!
cfallin created PR review comment:
Do we need the check for the start-bound here? Reading the code that produces the iterator and the
startedlogic above, it looks like the underlying cursor is always initialized to the first element, and we know the elements will be visited in sorted order; so is it sufficient to only check the end (and rename this tois_within_end_boundor something similar)? If not, could we add a comment here describing why we need this check too?
github-actions[bot] added the label cranelift on PR #12710.
fitzgen updated PR #12710.
fitzgen submitted PR review.
fitzgen created PR review comment:
Good catch. I also realized there was a bug when the range's start wasn't in the map. Pushed a commit to address both and some more testing.
fitzgen has enabled auto merge for PR #12710.
fitzgen added PR #12710 Add range iterators and immutable cursors for cranelift_bforest::Map to the merge queue
fitzgen merged PR #12710.
fitzgen removed PR #12710 Add range iterators and immutable cursors for cranelift_bforest::Map from the merge queue
Last updated: Mar 23 2026 at 16:19 UTC