Use component model resources
#47
Comments
|
Many of the execution context functions can be attached to graph once it is a resource. I'm not sure execution context makes sense as a resource since they shouldn't be shared (i.e they are tied to a specific instance of a graph so you will get into lifetime management issues). Doing this for large tensors could be make sense (i.e images) especially if being processed by a pipeline of components. |
abrown
added a commit
to abrown/wasi-nn-spec
that referenced
this issue
Oct 28, 2023
Now that component model `resource`s are specified and implemented, it should be possible to use the `resource` type for specifying tensors, graphs and execution contexts. Closes WebAssembly#47.
Merged
abrown
added a commit
to abrown/wasi-nn-spec
that referenced
this issue
Nov 9, 2023
Now that component model `resource`s are specified and implemented, it should be possible to use the `resource` type for specifying tensors, graphs and execution contexts. Closes WebAssembly#47.
abrown
added a commit
that referenced
this issue
Nov 9, 2023
Now that component model `resource`s are specified and implemented, it should be possible to use the `resource` type for specifying tensors, graphs and execution contexts. Closes #47.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once component model
resources are fully implemented, this specification should switch to using them for graphs, execution contexts, and possibly tensors (see #43).The text was updated successfully, but these errors were encountered: