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
Right now there is no type info because we coerce to the types we need at runtime. However, having type info to show intention is useful for documentation purposes. Whatever syntax we use here, it should be optional. It should also capture the concept of stack before/after states. In other words, the arguments represent values that need to be on the stack before the invocation, but we should also show what will be left on the stack. That will be zero or more items
The text was updated successfully, but these errors were encountered:
Right now there is no type info because we coerce to the types we need at runtime. However, having type info to show intention is useful for documentation purposes. Whatever syntax we use here, it should be optional. It should also capture the concept of stack before/after states. In other words, the arguments represent values that need to be on the stack before the invocation, but we should also show what will be left on the stack. That will be zero or more items
The text was updated successfully, but these errors were encountered: