number_prefix 0.1.0

Library for formatting numeric prefixes: kilo, giga, kibi.
docs.rs failed to build number_prefix-0.1.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: number_prefix-0.4.0

rust-number-prefix Build Status

This is a library for formatting numbers with numeric prefixes, such as turning "3000 metres" into "3 kilometres", or "8705 bytes" into "8.5 KiB".

View the Rustdoc

Installation

This crate, like all external crates, works very well with Cargo. So, to use it, add the following to your Cargo.toml:

[dependencies.number_prefix]
git = "https://github.com/ogham/rust-number-prefix.git"

Then import the number_prefix crate.

Usage

The function format_bytes returns either a pair of the resulting number and its prefix, or a notice that the number was too small to have any prefix applied to it. For example:

use number_prefix::{Decimal, Standalone, Prefixed};
match Decimal::prefix(8542_f32) {
	Standalone(bytes)   => println!("The file is {} bytes in size", bytes),
    Prefixed(prefix, n) => println!("The file is {:.0} {}B in size", n, prefix),
}

This will print out "The file is 8.5 KB in size". The {:.0} part of the formatting string tells it to restrict the output to only one decimal place. This value is calculated by repeatedly dividing the number by 1000 until it becomes less than that, which in this case results in 8.542, which gets rounded down. Because only one division had to take place, the function also returns the decimal prefix Kilo, which gets converted to its internationally-recognised symbol when formatted as a string.

If the value is too small to have any prefixes applied to it - in this case, if it's under 1000 - then the standalone value will be returned:

use number_prefix::{Decimal, Standalone, Prefixed};
match Decimal::prefix(705_f32) {
	Standalone(bytes)   => println!("The file is {} bytes in size", bytes),
    Prefixed(prefix, n) => println!("The file is {:.0} {}B in size", n, prefix),
}

This will print out "The file is 705 bytes in size", having chosen the other path to follow. In this particular example, the user expects different formatting for both bytes and kilobytes: while prefixed values are given more precision, there's no point using anything other than whole numbers for just byte amounts. This is why the function pays attention to values without any prefixes - they often need to be special-cased.

Binary Prefixes

This library also allows you to use the binary prefixes, which use the number 1024 (210) as the multiplier, rather than the more common 1000 (103). For example:

use number_prefix::{Binary, Standalone, Prefixed};
match Binary::prefix(8542_f32) {
	Standalone(bytes)   => println!("The file is {} bytes in size", bytes),
    Prefixed(prefix, n) => println!("The file is {:.0} {}B in size", n, prefix),
}

This will print out "The file is 8.3 KiB in size". A kibibyte is slightly larger than a kilobyte, so the number is smaller in the result; but other than that, it works in exactly the same way, with the binary prefix being converted to a symbol automatically.

Which type of prefix should I use?

There is no one way to answer this question! The prevailing theory is to use the binary prefixes for numbers of bytes, while still using the decimal prefixes for everything else. Computers work with powers of two, rather than powers of ten, and by using the binary prefixes, you get a more accurate representation about the amount of data.

Prefix Names

If you need to describe your unit in actual words, rather than just with the symbol, import the PrefixNames trait, which adds methods to output the prefix in a variety of formats. For example:

use number_prefix::{Decimal, Standalone, Prefixed, PrefixNames};
match Decimal::prefix(8542_f32) {
	Standalone(bytes)   => println!("The file is {} bytes in size", bytes),
    Prefixed(prefix, n) => println!("The file is {:.0} {}bytes in size", n, prefix.lower()),
}