New home in HdrHistogram org

Fixes #60.

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
-name = "hdrsample"
-version = "6.0.1"
+name = "hdrhistogram"
+version = "6.0.2"
 
 description = "A port of HdrHistogram to Rust"
 readme = "README.md"
@@ -10,17 +10,17 @@ authors = [
 	"Marshall Pierce <[email protected]>",
 ]
 
-documentation = "https://docs.rs/hdrsample"
-homepage = "https://github.com/jonhoo/hdrsample"
-repository = "https://github.com/jonhoo/hdrsample.git"
+documentation = "https://docs.rs/hdrhistogram"
+homepage = "https://github.com/HdrHistogram/HdrHistogram_rust"
+repository = "https://github.com/HdrHistogram/HdrHistogram_rust.git"
 
 keywords = ["sampling", "statistics", "analytics"]
 categories = ["data-structures", "development-tools::profiling"]
 
 license = "MIT/Apache-2.0"
 
 [badges]
-travis-ci = { repository = "jonhoo/hdrsample" }
+travis-ci = { repository = "HdrHistogram/HdrHistogram_rust" }
 
 [features]
 bench_private = [] # for enabling nightly-only feature(test) on the main crate to allow benchmarking private code

README.md

@@ -1,4 +1,4 @@
-# hdrsample
+# HdrHistogram_rust
 
 [![Crates.io](https://img.shields.io/crates/v/hdrsample.svg)](https://crates.io/crates/hdrsample)
 [![Documentation](https://docs.rs/hdrsample/badge.svg)](https://docs.rs/hdrsample/)
@@ -42,6 +42,10 @@ range and precision chosen. The amount of work involved in recording a sample is
 directly computes storage index locations such that no iteration or searching is ever involved
 in recording data values.
 
+If you are looking for FFI bindings to
+[`HdrHistogram_c`](https://github.com/HdrHistogram/HdrHistogram_c), you want the
+[`hdrhistogram_c`](https://crates.io/crates/hdrhistogram_c) crate instead.
+
 ## Interacting with the library
 
 HdrSample's API follows that of the original HdrHistogram Java implementation, with some
@@ -100,7 +104,7 @@ as the total number of recorded samples, or the value at a given quantile:
 use hdrsample::Histogram;
 let hist = Histogram::<u64>::new(2).unwrap();
 // ...
-println!("# of samples: {}", hist.count());
+println!("# of samples: {}", hist.len());
 println!("99.9'th percentile: {}", hist.value_at_quantile(0.999));
 ```
 
@@ -115,7 +119,7 @@ let hist = Histogram::<u64>::new(2).unwrap();
 // ...
 for v in hist.iter_recorded() {
     println!("{}'th percentile of data is {} with {} samples",
-        v.percentile(), v.value(), v.count_at_value());
+        v.percentile(), v.value_iterated_to(), v.count_at_value());
 }
 ```
 
@@ -176,7 +180,6 @@ not (yet) been implemented:
  - `DoubleHistogram`.
  - The `Recorder` feature of HdrHistogram.
  - Value shifting ("normalization").
- - Timestamps and tags.
  - Textual output methods. These seem almost orthogonal to HdrSample, though it might be
    convenient if we implemented some relevant traits (CSV, JSON, and possibly simple
    `fmt::Display`).

README.tpl

@@ -1,4 +1,4 @@
-# {{crate}}
+# HdrHistogram_rust
 
 [![Crates.io](https://img.shields.io/crates/v/hdrsample.svg)](https://crates.io/crates/hdrsample)
 [![Documentation](https://docs.rs/hdrsample/badge.svg)](https://docs.rs/hdrsample/)

src/lib.rs

@@ -36,6 +36,10 @@
 //! directly computes storage index locations such that no iteration or searching is ever involved
 //! in recording data values.
 //!
+//! If you are looking for FFI bindings to
+//! [`HdrHistogram_c`](https://github.com/HdrHistogram/HdrHistogram_c), you want the
+//! [`hdrhistogram_c`](https://crates.io/crates/hdrhistogram_c) crate instead.
+//!
 //! # Interacting with the library
 //!
 //! HdrSample's API follows that of the original HdrHistogram Java implementation, with some