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
In order to get the first 3 assignments we need to examine the type (ex. LocalVariableWrite) and then realize we need to build for a LocalVariableRead. If we look at last one we have to take two nested calls and realize we need to call bar instead of bar=. This is all doable but if you look at how this is done in JRuby and MRI today it looks more like:
This tree is more directly just buildable because it emits the accessor with the writer. For non-execution it makes sense that it has to be literal but for execution should we do something more like how it has been done or do we parse apart the write to determine the original read?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Let's look at some source:
And the nodes:
In order to get the first 3 assignments we need to examine the type (ex. LocalVariableWrite) and then realize we need to build for a LocalVariableRead. If we look at last one we have to take two nested calls and realize we need to call
bar
instead ofbar=
. This is all doable but if you look at how this is done in JRuby and MRI today it looks more like:This tree is more directly just buildable because it emits the accessor with the writer. For non-execution it makes sense that it has to be literal but for execution should we do something more like how it has been done or do we parse apart the write to determine the original read?
Beta Was this translation helpful? Give feedback.
All reactions