Confirmed users
1,016
edits
Oxidation: Difference between revisions
no edit summary
(Mention rayon in the context of encoding detection) |
No edit summary |
||
| Line 32: | Line 32: | ||
There are also technical challenges. | There are also technical challenges. | ||
* Compilation is slow. | * Compilation is slow. | ||
* Crossing the C++/Rust boundary can be difficult. | * [https://gist.github.com/zbraniecki/b251714d77ffebbc73c03447f2b2c69f Crossing the C++/Rust boundary can be difficult]. | ||
See "Blockers and obstacles" below for more details about work being done to remedy these weaknesses. | See "Blockers and obstacles" below for more details about work being done to remedy these weaknesses. | ||
| Line 128: | Line 128: | ||
* Japanese encoding detector: {{bug|1543077}} (shipped in Firefox 69) | * Japanese encoding detector: {{bug|1543077}} (shipped in Firefox 69) | ||
** '''Why Rust?''' Builds upon encoding_rs, has tiny FFI surface, subject matter prone to accesses past the bounds of a buffer. | ** '''Why Rust?''' Builds upon encoding_rs, has tiny FFI surface, subject matter prone to accesses past the bounds of a buffer. | ||
* Unicode Language Identifier: {{bug|1571915}} (shipped in Firefox 72) | |||
** '''Why Rust?''' Much faster, parser-heavy, easier to handle low-memory footprint thanks to `tinystr`. | |||
* Language Negotiation: {{bug|1581960}} (shipped in Firefox 72) | |||
** '''Why Rust?''' Ties into `unic-langid`, easier to handle list filtering and ordering. | |||
=== In progress === | === In progress === | ||