You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instructions are currently stored on the instruction result which makes them very dependent on passing around a ctrl_typevar to determine the type of operations. In practice, this means we must pass a type in every time we insert a new instruction into an ssa function in the refactor.
Proposed solution
We can avoid this if we store the types of values so that we can use these to determine the instruction type (if possible) instead.
Alternatives considered
No response
Additional context
No response
Submission Checklist
Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.
The text was updated successfully, but these errors were encountered:
Problem
Instructions are currently stored on the instruction result which makes them very dependent on passing around a ctrl_typevar to determine the type of operations. In practice, this means we must pass a type in every time we insert a new instruction into an ssa function in the refactor.
Proposed solution
We can avoid this if we store the types of values so that we can use these to determine the instruction type (if possible) instead.
Alternatives considered
No response
Additional context
No response
Submission Checklist
The text was updated successfully, but these errors were encountered: