Skip to content

Conversation

@vext01
Copy link
Contributor

@vext01 vext01 commented Aug 4, 2025

This scenario can indeed happen. I've just seen it with the Lua tests with the "really long trace" fix that's pending to merge.

Required for ykjit/yklua#129

// Can we still hit this case?
todo!();
// FIXME: implement the optimisation.
return op;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can delete the return op; line and the code will behave the same. If so, please force push an update.

This scenario can indeed happen. I've just seen it with the Lua tests
with the "really long trace" fix that's pending to merge.
@vext01
Copy link
Contributor Author

vext01 commented Aug 4, 2025

It's the same. Force pushed.

@ltratt ltratt added this pull request to the merge queue Aug 4, 2025
Merged via the queue into ykjit:master with commit a91e43c Aug 4, 2025
2 checks passed
@vext01 vext01 deleted the todo-to-fixme branch August 4, 2025 16:02
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