Add bitmaps-3.1.0

collector/benchmarks/README.md

@@ -15,6 +15,7 @@ There are three categories of benchmarks, **Primary**, **Secondary**, and
 These are real programs that are important in some way, and worth tracking.
 They mostly consist of real-world crates.
 
+- **bitmaps-3.1.0**: A bitmaps implementation. Stresses code handling traits.
 - **cargo-0.60.0**: The Rust package manager. A large program, and an important
   one in the Rust ecosystem.
 - **clap-3.1.6**: A command line argument parser. A crate used by many Rust
@@ -196,6 +197,9 @@ Rust code being written today.
   - Add the new entry to `collector/benchmarks/README.md`.
   - `git add` the `Cargo.lock` file, if it's not already part of the
     benchmark's committed code.
+    - If the benchmark has a `.gitignore` file that contains `Cargo.lock`,
+      you'll need to comment out that line so that `Cargo.lock` gets uploaded
+      in the PR.
 - Consider the benchmarking time for the benchmark.
   - First, measure the entire compilation time with something like this, by
     doing this within the benchmark directory is good:
@@ -207,7 +211,7 @@ Rust code being written today.
   - Second, compare the final crate time with these commands:
     ```
     target/release/collector bench_local +nightly --id Test \
-      --profiles=Check,Debug,Opt --scenarios=Full --include=$OLD,$NEW,helloworld
+      --profiles=Check,Debug,Opt --scenarios=Full --include=$NEW,helloworld
     target/release/site results.db
     ```
     Then switch to wall-times, compare `Test` against itself, and toggle the

collector/benchmarks/bitmaps-3.1.0/.cargo_vcs_info.json

@@ -0,0 +1,5 @@
+{
+  "git": {
+    "sha1": "6534d3b6e65ba2fe3fbc5e6e7b2087019095f9ee"
+  }
+}

collector/benchmarks/bitmaps-3.1.0/.github/dependabot.yml

@@ -0,0 +1,11 @@
+version: 2
+updates:
+- package-ecosystem: cargo
+  directory: "/"
+  schedule:
+    interval: daily
+  open-pull-requests-limit: 10
+  ignore:
+  - dependency-name: proptest-derive
+    versions:
+    - 0.3.0

collector/benchmarks/bitmaps-3.1.0/.github/workflows/ci.yml

@@ -0,0 +1,35 @@
+name: Continuous Integration
+on:
+  push:
+  pull_request:
+  schedule:
+    - cron: "0 0 1,15 * *"
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest, macOS-latest]
+        rust: [stable, beta, nightly]
+
+    steps:
+      - uses: hecrj/setup-rust-action@v1
+        with:
+          rust-version: ${{ matrix.rust }}
+      - uses: actions/checkout@v1
+      - name: Run tests (with all features)
+        run: cargo test --all-features
+      - name: Run tests (with no features)
+        run: cargo test --no-default-features
+
+  clippy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: hecrj/setup-rust-action@v1
+        with:
+          rust-version: stable
+          components: clippy
+      - uses: actions/checkout@v1
+      - name: Clippy
+        run: cargo clippy -- -D warnings

collector/benchmarks/bitmaps-3.1.0/.gitignore

@@ -0,0 +1,3 @@
+/target
+**/*.rs.bk
+#Cargo.lock

collector/benchmarks/bitmaps-3.1.0/0-println.patch

@@ -0,0 +1,12 @@
+diff --git a/src/bitmap.rs b/src/bitmap.rs
+index ba5d1b18..9542a890 100644
+--- a/src/bitmap.rs
++++ b/src/bitmap.rs
+@@ -27,6 +27,7 @@ where
+     BitsImpl<{ SIZE }>: Bits,
+ {
+     fn clone(&self) -> Self {
++        println!("testing");
+         Bitmap::from_value(self.data)
+     }
+ }

collector/benchmarks/bitmaps-3.1.0/CHANGELOG.md

@@ -0,0 +1,59 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project
+adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
+## [3.1.0] - 2021-04-30
+
+### ADDED
+
+-   The methods `first_false_index()` and `is_full()` have been added to `Bitmap`. (#12)
+
+### FIXED
+
+-   The previous version broke the `no_std` feature; it has now been restored. (#11)
+
+## [3.0.0] - 2021-04-26
+
+### CHANGED
+
+-   This crate now uses const generics, rather than the `typenum` crate, to encode numerical values
+    in types. This means you can now use plain integers in the `Bitmap` type, eg. `Bitmap<32>`,
+    rather than the old `Bitmap<typenum::U32>`. (#8, #9)
+
+### ADDED
+
+-   `Bitmap` now implements `Hash`, `Eq`, `PartialOrd` and `Ord`. (#7)
+-   The `as_value()` method has been added to `Bitmap`, to get a reference to the underlying value.
+    (#7)
+-   `bitmaps::Iter` now implements `Clone` and `Debug`. (#4)
+
+## [2.1.0] - 2020-03-26
+
+### ADDED
+
+-   There is now a `std` feature flag, on by default, which you can disable to get a `no_std` crate.
+
+## [2.0.0] - 2019-09-09
+
+### CHANGED
+
+-   `Bits` now does a lot less work, which is now being done instead by the `BitOps` trait on its
+    storage type. This turns out to improve compilation time quite considerably. If you were using
+    methods on `Bits` directly, they will have moved to `BitOps`.
+-   `Debug` now prints a single hex value for the entire bitmap, rather than deferring to the
+    storage type.
+-   `Iter` now takes a reference instead of a copy, which is more sensible for larger bitmaps.
+
+### ADDED
+
+-   `Bitmap` now implements `BitAnd`, `BitOr`, `BitXor`, their equivalent assignation traits, and
+    `Not`, meaning you can now use bitwise operators on them, even the very big array-of-u128 ones.
+-   A `Bitmap::mask()` constructor has been added, to construct bitmasks more efficiently, now that
+    there are bitwise operators to use them with.
+
+## [1.0.0] - 2019-09-06
+
+Initial release.

collector/benchmarks/bitmaps-3.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org