From 7f84ed40ba4d39a0a28e61e5e06345df075a11c8 Mon Sep 17 00:00:00 2001 From: Rahul Date: Tue, 8 Oct 2024 09:07:28 -0700 Subject: [PATCH] document set_input parameters usage --- crates/wasi-nn/src/backend/pytorch.rs | 3 +++ 1 file changed, 3 insertions(+) diff --git a/crates/wasi-nn/src/backend/pytorch.rs b/crates/wasi-nn/src/backend/pytorch.rs index 499184ec9a02..4ae82c9a979c 100644 --- a/crates/wasi-nn/src/backend/pytorch.rs +++ b/crates/wasi-nn/src/backend/pytorch.rs @@ -93,6 +93,9 @@ struct PytorchExecutionContext { id_type: Option, } +/// `set_input` supports multiple positional parameters with `Id::Index`, and a single named parameter with `Id::Name`. +/// `set_input` may be removed in the future, with `compute` method taking a list of named parameters. +/// See [PR #77](https://github.com/WebAssembly/wasi-nn/pull/77), at which point multiple named parameters for `Tensor` inputs is planned to be supported in pytorch backend. impl BackendExecutionContext for PytorchExecutionContext { fn set_input(&mut self, id: Id, input_tensor: &Tensor) -> Result<(), BackendError> { let kind = input_tensor.ty.try_into()?;