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
If each command recorded an order id then we could optionally display the commands in call order. Not sure how useful that is. I'm just worried that devs will want to see what they did, not just results of what they did.
Like the mapAsync being translated in bufferUpdateData, I think the user would like to see mapAsyc, getMappedRange, unmap? or not?
The text was updated successfully, but these errors were encountered:
I don't know if this would be useful or not but, the trace doesn't record what you did. It records the effect of what you did.
So,
Will show up in the trace as
If each command recorded an order id then we could optionally display the commands in call order. Not sure how useful that is. I'm just worried that devs will want to see what they did, not just results of what they did.
Like the
mapAsync
being translated inbufferUpdateData
, I think the user would like to seemapAsyc
,getMappedRange
,unmap
? or not?The text was updated successfully, but these errors were encountered: