sentencepiece-rs
SentencePiece model loading, normalization, encoding, and decoding in pure Rust. Load a .model file, tokenize text, and decode tokens back into text.
Install
[]
= "0.2"
Quick Start
use SentencePieceProcessor;
Decode Pieces
use SentencePieceProcessor;
let sp = open?;
let text = sp.decode?;
assert_eq!;
# Ok::
Extra Options
use SentencePieceProcessor;
let mut sp = open?;
sp.set_encode_extra_options?;
let ids = sp.encode_to_ids?;
# Ok::
Supported options: bos, eos, reverse, unk_piece.
Compatibility Notes
The crate reads standard SentencePiece model protobufs and uses the embedded normalizer trie, so normal .model files should load without drama. The runtime behavior follows the C++ implementation, but this is not a line-by-line rewrite.
The big missing chunk is training. Bring your own existing model for now.
Documentation
References
- Original SentencePiece repo: google/sentencepiece
- Paper: arXiv PDF
Test Locally
License and Terms of Use
This crate is licensed under the Apache License, Version 2.0. See ./LICENSE.
The original SentencePiece source is also licensed under the Apache License, Version 2.0. This crate is a Rust reimplementation that uses the upstream source as the behavioral reference; it is not a C++ binding and does not link against the C++ library.
Apache 2.0 is permissive. In normal-human terms, you can use, modify, distribute, sublicense, and ship derivative work, including commercially, as long as you follow the license terms.
If you redistribute this crate, the upstream source, or a modified version, keep the important bits intact:
- include a copy of the Apache 2.0 license
- preserve copyright, patent, trademark, and attribution notices that apply
- mark modified files when you change Apache-licensed source
- include upstream
NOTICEcontent if a distributed upstream package includes one - do not imply Google or SentencePiece trademark endorsement
The software is provided as-is, without warranty, and the Apache 2.0 patent grant terminates if you sue over patent infringement involving the licensed work. That is the deal. Pretty reasonable, honestly.
This README is a practical summary, not legal advice. The actual license text in ./LICENSE and the upstream SentencePiece license are the source of truth.