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 artifact graph is a graph representing the output of a KCL program, where nodes of the graph are objects like planes, paths, extrusions, etc. and edges of the graph are the relationships between them, like this extrusion is a linear extrude of that path, and this path is on that plane. Currently, the artifact graph is generated in TS by intercepting the requests and responses of engine calls made by the KCL interpreter.
There are a few motivations for moving this to Rust.
It would continue to work without communicating with the engine (AKA mock execution) during sketch mode
We believe it would be easier to maintain in Rust
Drawbacks
More data will need to cross the WASM boundary. Contrast this with how it is now where TS code derives the information from the engine messages, which have to cross the boundary anyway in order to use the WebSocket.
The text was updated successfully, but these errors were encountered:
The artifact graph is a graph representing the output of a KCL program, where nodes of the graph are objects like planes, paths, extrusions, etc. and edges of the graph are the relationships between them, like this extrusion is a linear extrude of that path, and this path is on that plane. Currently, the artifact graph is generated in TS by intercepting the requests and responses of engine calls made by the KCL interpreter.
There are a few motivations for moving this to Rust.
Drawbacks
The text was updated successfully, but these errors were encountered: