Stream: git-wasmtime

Topic: wasmtime / PR #11464 Cranelift: Split out computation of ...

Wasmtime GitHub notifications bot (Aug 19 2025 at 20:12):

fitzgen opened PR #11464 from fitzgen:generalize-cursor-methods to bytecodealliance:main:

This allows users to query what the next/prev position in their traversal would be without actually changing the cursor's current location. Otherwise, they would have to do something like

cursor.next_block();
let next_pos = cursor.current_position();
cursor.prev_block();

These new methods aren't used anywhere yet, other than the implementation of the cursor-position-updating methods they were split out from, but it seems useful to expose. I almost needed it for some inlining stuff, but ultimately took a slightly different approach.

<!--
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.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

Wasmtime GitHub notifications bot (Aug 19 2025 at 20:12):

fitzgen requested abrown for a review on PR #11464.

Wasmtime GitHub notifications bot (Aug 19 2025 at 20:12):

fitzgen requested wasmtime-compiler-reviewers for a review on PR #11464.

Wasmtime GitHub notifications bot (Aug 20 2025 at 22:11):

abrown submitted PR review.

Wasmtime GitHub notifications bot (Aug 20 2025 at 22:34):

abrown merged PR #11464.

Last updated: Dec 06 2025 at 06:05 UTC