| { | ||
| "git": { | ||
| "sha1": "6523fc7b89edf6b095c4c8b95cfb306e0e06061d" | ||
| "sha1": "589719b3fc86a8dd868c88315cb4389c6b1614dc" | ||
| } | ||
| } |
+2
-2
@@ -16,4 +16,4 @@ # THIS FILE IS AUTOMATICALLY GENERATED BY CARGO | ||
| name = "bitvec" | ||
| version = "0.10.0" | ||
| authors = ["myrrlyn <myrrlyn@outlook.com>"] | ||
| version = "0.10.1" | ||
| authors = ["myrrlyn <self@myrrlyn.dev>"] | ||
| description = "A crate for manipulating memory, bit by bit" | ||
@@ -20,0 +20,0 @@ homepage = "https://myrrlyn.net/bitvec" |
+13
-0
@@ -5,2 +5,15 @@ # Changelog | ||
| ## 0.10.1 | ||
| Bugfix for [Issue #7](https://github.com/myrrlyn/bitvec/issues/7). | ||
| `BitSlice::count_ones` and `BitSlice::count_zeros` counted the total number of | ||
| bits present in a slice, not the number of bits set or unset, when operating | ||
| inside a single element. | ||
| The small case used `.map().count()`, but the large case correctly used | ||
| `.map().filter().count()`. The missing `.filter()` call, to remove unset or set | ||
| bits from the counting, was the cause of the bug. | ||
| Thanks to GitHub user [@geq1t](https://github.com/geq1t) for the report! | ||
| ## 0.10.0 | ||
@@ -7,0 +20,0 @@ |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is too big to display