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
The current transform behavior for cyclic nodes is not robust. I slapped together a ctx with seen and lazy resolutions, but currently lazilyResolve is limited to root nodes, whereas to support this it needs to be able to handle any composite node kind (see Node.transform at ark/schema/node.ts).
My initial thoughts were a scope should keep create a unique id per transformation when the root transform call is made.
Then each id in seen would be lazily resolved to that id prefixed with the transform id.
The text was updated successfully, but these errors were encountered:
The current transform behavior for cyclic nodes is not robust. I slapped together a ctx with seen and lazy resolutions, but currently
lazilyResolve
is limited to root nodes, whereas to support this it needs to be able to handle any composite node kind (see Node.transform at ark/schema/node.ts).My initial thoughts were a scope should keep create a unique id per transformation when the root transform call is made.
Then each
id
in seen would be lazily resolved to that id prefixed with the transform id.The text was updated successfully, but these errors were encountered: