|0.0.11||Aug 1, 2021|
|0.0.10||Jul 29, 2021|
|0.0.3||Sep 22, 2020|
|0.0.1||Aug 26, 2020|
#794 in Parser implementations
105 downloads per month
Used in 4 crates (2 directly)
TAML is a configuration file format combining some aspects of Markdown, CSV, TOML, YAML and Rust.
As configuration language, TAML's main design goals are to be:
- Unambiguous and Debuggable
Since it is mainly human-oriented and the same data can be represented in multiple ways, there is in fact no serializer in this library. If you need a data transfer format, pretty much anything else will give you better performance.
That said, I believe that for human-written files, TAML offers a great balance between brevity and simplicity, with more than sufficient performance.
A command line validator and formatter is available in the
Serde-intergration can be found in
See https://taml.schichler.dev for documentation on the format itself.
Please use cargo-edit to always add the latest version of this library:
cargo add taml
TODO: Add a good example file here.
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Code of Conduct
taml strictly follows Semantic Versioning 2.0.0 with the following exceptions:
- Invalid TAML becoming valid is considered a feature addition.
- The minor version will not reset to 0 on major version changes (except for v1).
Consider it the global feature level.
- The patch version will not reset to 0 on major or minor version changes (except for v0.1 and v1).
Consider it the global patch level.
This includes the Rust version requirement specified above.
Earlier Rust versions may be compatible, but this can change with minor or patch releases.
Which versions are affected by features and patches can be determined from the respective headings in CHANGELOG.md.