fix: back frame in abstracted operations as functions #62
Conversation
This file contains 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
lumasepa
requested review from
navasvarela,
Jmgr,
manel1874,
jcabrero,
pablojhl and
nilmemo
Jmgr
approved these changes
Nov 26, 2024
pablojhl
approved these changes
Nov 26, 2024
navasvarela
approved these changes
Nov 26, 2024
navasvarela
deleted the
fix/backframe-in-abstracted-operations-as-functions
branch
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.
Fixes
Back frame in operations built in abstracted functions was pointing to the wrong frame, one back when it should be two frames back.
Changes
Change all abstracted operations functions to call backframe twice pointing to the right back frame