diff --git a/Cargo.toml b/Cargo.toml index 6326c9d..3b00694 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "wrapping_coords2d" -version = "0.1.5" # remember to update html_root_url +version = "0.1.6" # remember to update html_root_url authors = ["Fabio A. Correa Duran "] categories = ["caching", "memory-management"] description = "Translate between 1D indices and 2D coordinates with wrapping" diff --git a/README.md b/README.md index 3d0063d..f4c3a85 100644 --- a/README.md +++ b/README.md @@ -16,4 +16,4 @@ See more examples in the documentation for the [`wrapping_coords2d`](https://doc ## Why not create iterators to the neighbors of a cell? -In an ECS design, indices make more sense than iterators: if a game world or a model landscape has several components, such as color, depth, and fertility, it makes sense to keep each component in its own vector. The simplest approach is to use indices on them. However, I am open to a pull request contributing code for iterators into neighbors. +Indices make more sense than iterators in an ECS design. It's generally more idiomatic to use a `for` loop with indices than iterator chains. if a game world or a model landscape has several components, such as color, depth, and fertility, it makes sense to keep each component in its own vector. The simplest approach is to use indices on them. However, I am open to a pull request contributing code for iterators into neighbors. diff --git a/src/lib.rs b/src/lib.rs index 7a51e9e..606d6a8 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -15,7 +15,7 @@ limitations under the License. */ -#![doc(html_root_url = "https://docs.rs/wrapping_coords2d/0.1.5")] +#![doc(html_root_url = "https://docs.rs/wrapping_coords2d/0.1.6")] //! Rust crate to translate between 1D indices and 2D coordinates with wrapping https://crates.io/crates/wrapping_coords2d //!