Replace lambda with method to avoid YJIT crash #12
Conversation
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
wt-l00
approved these changes
Jan 28, 2026
AZQ1994
force-pushed
the
lambda-to-method-in-renderer
branch
from
c78fd36 to
8487301
Compare
AZQ1994
force-pushed
the
lambda-to-method-in-renderer
branch
from
8487301 to
917e03d
Compare
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.
YJIT was crashing, likely due to lambda incompatibility.
Switched the lambda implementation to an equivalent method (no API change).
FYI: Using lambda with define_method also triggers YJIT crashing.
So although templates were written in lambda format, it is converted to method definition and processed by class_eval.