Top Tweets for #bitvec
As such, I (myrrlyn) have written a draft version of a 1.0 release using `cfg(target_has_atomic)`. It also introduces two newtypes, `Atom<T>` and `Isotope<T>`, that should make its use in projects such as #bitvec easier.
Check it out here: https://t.co/bkhWsgt8uo
moving into that house, and then unpacking boxes both real and imaginary that have been packed up for about as long as #bitvec itself has existed.
But today, I have version 1.0.1! This release is maintenance and complaint fixes only. It includes:
I know Rust's rules and #bitvec's additional demands fairly well, so I instinctively obey them, and don't really push boundaries in user code rather than in my implementation's edge cases.
So *to me*, `bits![static mut]` was fine, because I always used it correctly.
But.
It’s done. With the Serde support module reëngineered, the #bitvec 1.0.0 release candidate is API-complete.
I need to finish restoring code coverage in the test suite, and write a *lot* of documentation. But we’re on track to end this.
And both of them have defaults (`<O: BitOrder = Lsb0, T: BitStore = usize>`), so it's fine to simply not specify them. But Rust does implicit arguments from the right: see `HashMap<K, V, S = RandomState>`, or `Vec<T, A = Global>`.
…#bitvec should be `<T, O>`, not `<O, T>`.
I understand *why* C, C++, and D forbid taking the address of a bitfield. (I don't know offhand if Zig allows it or not.) But the ability to take a bit's address is an immensely powerful capability in #bitvec and one I hope I can impart to other languages as I mature the project.
2. This discusses the rules that enable #bitvec to have the capability of type-level alias awareness, and the algorithm that allows runtime deäliasing upon request. https://t.co/I5TnGlc7FT
This bug is impossible to produce in #bitvec, and has been since early 2019. After requests and concept drafts by users, since early 2020 bitvec has been able to eliminate both the original bug and the cost of the fix described here. No wariness needed. https://t.co/ysisoEgGeA
#bitvec 0.21 is published. It contains a few small new APIs; the main reason for the minor bump rather than a patch bump is that `bitarr!` no longer produces typenames; `BitArr!` produces types and `bitarr!` produces values.
In May I will do a final pass over the book and associated support material. In June I will do a final review.
On June 28th, 2021, #bitvec will turn three years old, and I will publish 1.0.
Today I released 0.20.0, the last step in the minor series. #bitvec is feature-complete, API-compatible with today's standard library, and performant.
This begins the final countdown to 1.0. The 0.20 series is the release candidate for 1.0.
I have just published #bitvec 0.20.0.
This took me a while to do, and touched some more of the core components of the crate.
This completes the last features needed for 1.0
I get a lot of user stories from people who use #bitvec to view bit-patterns in memory, which is cool, but this is the first I've seen from someone using it to create a data structure, which is a pattern I have sought to support since the beginning.
My favorite kind of user is the kind I met today: somebody emailed me asking if I could check their work; they were having a bug, weren't sure why. and wondered if I could make sure it wasn't a #bitvec internal error.
At 12k lines and half a megabyte, it's not exactly small, but CE can still process it pretty quickly.
Now I can paste this in, sketch some functions that call the #bitvec API, and immediately see what kind of instruction output I get!
`cargo-objdump` is a great tool, but the Compiler Explorer is still incredibly convenient and powerful, and I prefer using it where possible.
To that end, here is a snapshot of current #bitvec, reduced to one file for easy copy/paste into any environment: https://t.co/Z28hv9t30I
Last Seen Hashtags on Sotwe
NoLimit() filter:videos
Seen from France
colmek sendiri
Seen from Singapore
incestuosa
Seen from Argentina
xhamster
Seen from Germany
Sustainability_Roadmap
Seen from United States
tocil
Seen from France
darlinginthefranxx
Seen from United States
ometv tongue
Seen from Thailand
Sydney
Seen from Indonesia
FictionSoldAsRealLife
Seen from United States
Most Popular Users
Elon Musk 
@elonmusk
240.2M followers
Barack Obama
@barackobama
119.3M followers
Donald J. Trump
@realdonaldtrump
111.6M followers
Cristiano Ronaldo
@cristiano
109.4M followers
Narendra Modi
@narendramodi
106.9M followers
Rihanna
@rihanna
97.4M followers
NASA
@nasa
92.1M followers
Justin Bieber
@justinbieber
90.7M followers
KATY PERRY
@katyperry
87.1M followers
Taylor Swift
@taylorswift13
80.9M followers
Lady Gaga
@ladygaga
72.5M followers
Kim Kardashian
@kimkardashian
69.5M followers
Virat Kohli
@imvkohli
69M followers
YouTube
@youtube
68.6M followers
Bill Gates
@billgates
63.5M followers
The Ellen Show
@theellenshow
62.5M followers
CNN
@cnn
61.9M followers
Neymar Jr
@neymarjr
61.6M followers
X
@x
60.9M followers
Selena Gomez
@selenagomez
60.2M followers