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
Our new DSL can express variadic stack effects using array[oparg] and even caters for conditions (foo if (C-expression)). But four opcodes (SEND, JUMP_IF_FALSE_OR_POP, JUMP_IF_TRUE_OR_POP, FOR_ITER) have different stack effects depending on whether they jump. How should we express that? New syntax or a magic constant in C-expression above?
The short term answer is "don't worry about". It is simple enough to workaround in the tooling for now.
In the longer term we'll need to add JUMP_AND_POP() macros (or something like that) to complement the JUMPBY() macros we currently have. Plus the tools will need to understand these macros.
Our new DSL can express variadic stack effects using
array[oparg]
and even caters for conditions (foo if (C-expression)
). But four opcodes (SEND
,JUMP_IF_FALSE_OR_POP
,JUMP_IF_TRUE_OR_POP
,FOR_ITER
) have different stack effects depending on whether they jump. How should we express that? New syntax or a magic constant inC-expression
above?@markshannon
The text was updated successfully, but these errors were encountered: