| Crates.io | data-encoding-v3 |
| lib.rs | data-encoding-v3 |
| version | 0.1.0 |
| created_at | 2025-04-13 11:42:51.082857+00 |
| updated_at | 2025-04-13 11:42:51.082857+00 |
| description | Development branch of data-encoding 3.0.0 |
| homepage | |
| repository | https://github.com/ia0/data-encoding |
| max_upload_size | |
| id | 1631758 |
| size | 125,636 |
:warning: It is strongly discouraged to use this crate at this time. There are no guarantees whatsoever (correctness, stability, documentation, etc). This warning will be updated as new versions are published.
This crate is the development branch of data-encoding@3.0.0. It is provided as a workaround to the
Cargo pre-release issues.
It will obey the following rules:
data-encoding-v3@0.1.0data-encoding-v3@1.0.0data-encoding-v3@0.x.y represents data-encoding@3.0.0-x.ydata-encoding-v3@1.0.0 corresponds to data-encoding@3.0.0data-encodingIn particular, the data-encoding crate won't have any 3.0.0 pre-release version. This crate
should be used instead. To minimize code changes (v3 won't break simple usages of v2), you can
modify your Cargo.toml from using data-encoding:
[dependencies]
data-encoding = "2.9.0"
to using data-encoding-v3 while preserving the crate name:
[dependencies]
data-encoding = { package = "data-encoding-v3", version = "0.1.0" }
When data-encoding-v3 reaches 1.0.0, then data-encoding will reach 3.0.0 too, and the
Cargo.toml should use data-encoding again:
[dependencies]
data-encoding = "3.0.0"