1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216
/*! [](https://travis-ci.org/bcmyers/num-format) [](https://crates.io/crates/num-format) [](https://docs.rs/num-format/)  A Rust crate for producing string-representations of numbers, formatted according to international standards, e.g. - `"1,000,000"` for US English - `"10,00,000"` for Indian English - `"1 000 000"` for French French # Picking a format Formatting options (e.g. which thousands separator to use, what the minus sign looks like, etc.) are represented by the [`Format`] trait. This crate offers three concrete implementations of the [`Format`] trait... ### `Locale` The [`Locale`] type is a programatically generated enum representing formatting standards from the [Common Locale Data Repository], which is maintained by the [Unicode Consortium] and used by Apple in macOS and iOS, by LibreOffice, by IBM in AIX, among others. ```rust use num_format::{Format, Locale}; fn main() { let format = Locale::en; assert_eq!(format.decimal(), '.');; assert_eq!(format.minus_sign(), "-"); assert_eq!(format.separator(), Some(',')) // ... } ``` ### `Environment` The [`Environment`] type allows you to access your system's locale settings via the `LC_ALL` environment variable. If you're familiar with C, it pulls system information using the [`setlocale`] and [`localeconv`] functions in the C standard library. For more details, see [`Environment`]. ### `CustomFormat` Allows for the creation of your own, custom format. For more details, see [`CustomFormat`]. # Creating a string representation Once you have selected a format, you can turn number types into formatted string representations via any of three principle APIs... ### `ToFormattedString` Using the [`ToFormattedString`] trait is the simplist API, just call [`to_formatted_string`] on a type that implements it (all the number types in the standard library implement it) with a desired format. That said, using [`ToFormattedString`] will always heap allocate; so it is the slowest of the three APIs and cannot be used in a `no_std` environment. ```rust # use cfg_if::cfg_if; cfg_if! { if #[cfg(feature = "std")] { use num_format::{Locale, ToFormattedString}; fn main() { let s = 1000000.to_formatted_string(&Locale::en); assert_eq!(&s, "1,000,000"); } # } else { fn main() {} } } ``` ### `Buffer` Using the [`Buffer`] type is the fastest API, as it does **not** heap allocate. Instead, the formatted representation is written into a stack-allocated buffer. As such, you can use it in a `no_std` environment. Although this API is available for all the number types in the standard library, it is **not** available for third party types like [`num_bigint::BigInt`] since their maximum size cannot be known in advance. ```rust use num_format::{Buffer, Locale}; fn main() { // Create a stack-allocated buffer... let mut buf = Buffer::default(); // Write '"1,000,000"' into the buffer... buf.write_formatted(&1000000, &Locale::en); assert_eq!(buf.as_str(), "1,000,000"); } ``` ### `WriteFormatted` The [`WriteFormatted`] trait is in between the other two APIs. You can write a formatted representation into any type that implements [`WriteFormatted`] (all the types in the standard library that implement [`io::Write`] or [`fmt::Write`] implement it, such as [`Vec`], [`String`], [`File`], etc.). If you're writing a number type that can use the [`Buffer`] API (e.g. any number type in the standard library), there is **no** heap allocation. That said, you can also use this API with types where the [`Buffer`] API will not work, like [`num_bigint::BigInt`], in which case there will be heap allocations used. This trait is **not** available in a `no_std` environment. ```rust # use cfg_if::cfg_if; cfg_if! { if #[cfg(feature = "std")] { use num_format::{Locale, WriteFormatted}; fn main() { // Create a writer... let mut writer = String::new(); // Could also be Vec::new(), File::open(...), ... // Write '"1,000,000"' into the writer... writer.write_formatted(&1000000, &Locale::en); assert_eq!(&writer, "1,000,000"); } # } else { fn main() {} } } ``` # Extra features | Available features | What to put in your `Cargo.toml` | | :----------------- | :------------------------------------------------------------ | | `no_std` | `num-format = { version = "0.1", default-features = false }` | | `num-bigint` | `num-format = { version = "0.1", features = ["num-bigint"] }` | | `serde` | `num-format = { version = "0.1", features = ["with-serde"] }` | # License **num-format** is licensed under either of: - [The Apache License, Version 2.0], or - [The MIT license] at your option. [`Buffer`]: struct.Buffer.html [Common Locale Data Repository]: https://en.wikipedia.org/wiki/Common_Locale_Data_Repository [`CustomFormat`]: format/struct.CustomFormat.html [`Environment`]: format/struct.Environment.html [`File`]: https://doc.rust-lang.org/std/fs/struct.File.html [`fmt::Write`]: https://doc.rust-lang.org/std/fmt/fn.write.html [`Format`]: format/trait.Format.html [`io::Write`]: https://doc.rust-lang.org/std/io/trait.Write.html [`Locale`]: format/enum.Locale.html [`localeconv`]: https://www.gnu.org/software/libc/manual/html_node/The-Lame-Way-to-Locale-Data.html#The-Lame-Way-to-Locale-Data [`num_bigint::BigInt`]: https://docs.rs/num-bigint/0.2.2/num_bigint/struct.BigInt.html [`setlocale`]: https://www.gnu.org/software/libc/manual/html_node/Setting-the-Locale.html [`String`]: https://doc.rust-lang.org/std/string/struct.String.html [The Apache License, Version 2.0]: http://www.apache.org/licenses/LICENSE-2.0 [The MIT license]: http://opensource.org/licenses/MIT [`ToFormattedString`]: trait.ToFormattedString.html [`to_formatted_string`]: trait.ToFormattedString.html#method.to_formatted_string [Unicode Consortium]: https://en.wikipedia.org/wiki/Unicode_Consortium [`Vec`]: https://doc.rust-lang.org/std/vec/struct.Vec.html [`WriteFormatted`]: trait.WriteFormatted.html */ #![cfg_attr(not(feature = "std"), no_std)] #![deny(dead_code)] #![deny(deprecated)] #![deny(missing_copy_implementations)] #![deny(missing_debug_implementations)] #![deny(missing_docs)] #![deny(trivial_casts)] #![deny(trivial_numeric_casts)] #![deny(unused_extern_crates)] #![deny(unused_imports)] #![deny(unused_macros)] #![deny(unused_mut)] #![deny(unused_results)] #![deny(unused_parens)] #![deny(unused_unsafe)] #![deny(unused_variables)] #![doc(html_root_url = "https://docs.rs/num-format/0.2.1")] #[cfg(feature = "with-serde")] #[macro_use] extern crate serde; mod buffer; mod constants; mod custom_format; mod custom_format_builder; mod environment; mod error; mod error_kind; mod format; mod grouping; mod impls; mod locale; mod to_formatted_str; mod to_formatted_string; pub mod utils; mod write_formatted; pub use self::buffer::Buffer; pub use self::custom_format::CustomFormat; pub use self::custom_format_builder::CustomFormatBuilder; pub use self::error::Error; pub use self::error_kind::ErrorKind; pub use self::format::Format; pub use self::grouping::Grouping; pub use self::locale::Locale; pub use self::to_formatted_str::ToFormattedStr; #[cfg(feature = "std")] pub use standard::*; #[cfg(feature = "std")] mod standard { pub use super::environment::Environment; pub use super::to_formatted_string::ToFormattedString; pub use super::write_formatted::WriteFormatted; } mod sealed { pub trait Sealed {} }