Skip to content

More natural indexing for BitVec #1

@bovee

Description

@bovee

It would be nice to write bitvec[1] = true rather than bitvec.set(1, true).

This is essentially blocked on:
rust-lang/rfcs#997

The standard library bit vector has a hacky workaround for getting (and no way to set) indices, but this won't work for us for ranges:
https://doc.rust-lang.org/1.2.0/src/collections/bit.rs.html#168-180

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions