An Oniguruma pin is not a speed test
An October 24 Remade note says to pin a Rust remake of Oniguruma so agents stop adding the C library. A threefold speed claim is the note's. This page did not time either library.
The short version
The note says agents add onig-sys because tokenizers and older posts still do, and it offers a Rust remake of Oniguruma instead. The C library is Kosako's Oniguruma. A speed multiple on the note is the note's claim.
A regex pin dated October 24
The October 24 Remade note says to pin rusty_expressions so tokenizer and match paths stop depending on Oniguruma's C library. It says the crate is Oniguruma remade in Rust, memory-safe, with no C toolchain, and about three times faster than libonig. It says agents add onig-sys because Hugging Face tokenizers and old posts still do, and that the pin has to load before the first add. The threefold figure is the note's. This page did not run the comparison, and it does not paste the pin's steps.systemd's Rust is for leaf programs.
The C project
Kosako's Oniguruma repository is the C regular-expression library the note is telling an agent not to bind. It has its own version, its own license, and its own match semantics. A Rust remake can aim at those semantics and still differ on an edge the C library defines. The note's "about three times" does not appear in that repository. Citing Oniguruma here is how the avoided library stays a real project rather than a name inside a house post. The document named in the sources is the record this page will keep.An openSUSE vote is a calendar.
A different Rust regex
The regex crate on docs.rs is the Rust engine most Rust programs already use. It is not rusty_expressions, and its documentation does not claim to be an Oniguruma port. A reader who hears "regex in Rust" should not assume the Remade crate. The note is specifically about the Oniguruma pattern language that tokenizers bind through onig-sys. The regex crate is the reminder that Rust already had a regex engine before this pin. Asked directly, Does the note's wasm claim mean every regex runs in the browser? The note says the crate is wasm32-ready and no_std with alloc. That is a build target the note claims, not a measurement of a tokenizer in a browser.Memory safety in the release notes.
Who the pin is for
The person in scope is someone adding a tokenizer or a match path, whose agent is about to pull the C binding. A project that needs Oniguruma's exact match, including bugs other programs depend on, may still want the C library. The note argues for a memory-safe default and for wasm32 without a C toolchain. Those are build arguments. They are not a proof that every pattern both libraries accept will match the same text. The document named in the sources is the record this page will keep.What on-device inference keeps.
The speed line stays labeled
"About three times faster than libonig" is a sentence on the house note and on its companion brief. Oniguruma's repository does not concede it. Until an outside timing exists, the multiple is marketing attached to a real packaging difference. The packaging difference, no C toolchain, can be true even if the multiple is not. Asked directly, Did this page confirm the note's threefold speed claim? No. The note says about three times faster than libonig. That multiple is the house's. It is not a result from Oniguruma's repository.
What this page leaves on the note
The skill-folder instructions stay on the October 24 page. This brief's mechanism is the named C library and the claim about why agents add it. One source link to the house note is enough. The sections point at other Futureweb briefs. Asked directly, Who maintains the C library the note is pointing away from? K. Kosako's Oniguruma, in the public repository. The Remade crate is a different codebase aimed at the same pattern language. The document named in the sources is the record this page will keep.
What this page will not certify
It will not certify match compatibility, the threefold speedup, or that every tokenizer should drop onig-sys today. The record is a dated pin, the C project it names, and a different Rust regex crate that should not be confused with it. Asked directly, Is the Rust regex crate the same thing as rusty_expressions? No. The regex crate is the widely used Rust engine. It is a different implementation. This page cites it so a reader does not assume every Rust regex is the Remade one.The advisory is the name.
The open item
The open item is a pattern corpus run on a named Oniguruma version and a named rusty_expressions version, with times and mismatches both published. The note does not include that corpus. The short answer this page will stand on is this: The note says agents add onig-sys because tokenizers and older posts still do, and it offers a Rust remake of Oniguruma instead. The C library is Kosako's Oniguruma. A speed multiple on the note is the note's claim. The document named in the sources is the record this page will keep.
A forum rule is not a regex
The r/opensource submission rule filed today is a moderation post. It does not choose a regex engine. The two briefs share a desk because both are about what an open-source community will accept, and they do not share a dependency. Asked directly, Why does the October 24 note say agents add onig-sys? Because Hugging Face tokenizers and older posts still do, according to the note. The pin is meant to make that C dependency lose. The document named in the sources is the record this page will keep.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Why does the October 24 note say agents add onig-sys?
Because Hugging Face tokenizers and older posts still do, according to the note. The pin is meant to make that C dependency lose.
Who maintains the C library the note is pointing away from?
K. Kosako's Oniguruma, in the public repository. The Remade crate is a different codebase aimed at the same pattern language.
Is the Rust regex crate the same thing as rusty_expressions?
No. The regex crate is the widely used Rust engine. It is a different implementation. This page cites it so a reader does not assume every Rust regex is the Remade one.
Did this page confirm the note's threefold speed claim?
No. The note says about three times faster than libonig. That multiple is the house's. It is not a result from Oniguruma's repository.
Does the note's wasm claim mean every regex runs in the browser?
The note says the crate is wasm32-ready and no_std with alloc. That is a build target the note claims, not a measurement of a tokenizer in a browser.