Skip to content
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

Expose getEncodingNameForModel in wasm version? #123

Open
jens-ghc opened this issue Nov 14, 2024 · 0 comments
Open

Expose getEncodingNameForModel in wasm version? #123

jens-ghc opened this issue Nov 14, 2024 · 0 comments

Comments

@jens-ghc
Copy link

Would it be possible to expose the function getEncodingNameForModel that's available in the javascript version also in the wasm version of the library?

The wasm version currently exposes encoding_for_model and get_encoding and both create a tokenizer instance immediately. For our uses, we'd like to first translate the model name to the underlying encoding and then instantiate the tokenizer with get_encoding ourselves. This would allow us to cache and reuse a single tokenizer across multiple models that use the same encoding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant