-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
string input support? #3992
Comments
To make it supported in ExecuTorch I think it needs to be supported in the upstream PyTorch first. I'm not sure if we have a plan to support this feature request. @iseeyuan may know. |
@dbort since Martin is out, any ideas on this one? |
Asking about this internally. Like Martin said, EValue doesn't support String, so I don't expect we'd have first-class support. The alternative is to provide some kind of wrapper to turn the string into a Tensor, but that will result in either a fully-dynamic-shaped input or an upper-bounded and padded input. |
@soulx0 do you have a specific use case for this? There are a bunch of trade-offs, so it would help us understand the possible solutions. |
String processing is not supported by export nor do I think its planned cc @angelayi |
Closing because we have no plans do to this in the near future. The first step would probably require changes on the pytorch/pytorch export side. |
similar to : https://github.com/tensorflow/tensorflow/issues/21213
and how tflite does: tensorflow/tensorflow#21213
could executorch do better on string inputs?
The text was updated successfully, but these errors were encountered: