robinst
u/robinst
I've recently built a demo page for my linkify library using Wasm where you can try it out live in the browser: https://robinst.github.io/linkify/
I think being able to do that with Rust is a unique selling point for the language! For certain kinds of libraries, having a demo page is useful for people evaluating it. It means they don't have to set up their own little example project or add it to their project first.
If you have a library that could benefit from a demo page, consider setting one up too! It was actually pretty simple once I figured out the webpack config. See source here.
Have a timestamp and not sure what format/timezone it's in? Tiny website to help
whatsthistimestamp.com/I'm happy to announce the 0.2.0 release of fancy-regex, a library built on top of the regex crate to add support for fancy features such as look-ahead/behind and backreferences.
See the README for a more detailed introduction. Note that supporting fancy features means giving up the linear runtime guarantee of the regex crate - you have been warned :).
This release contains a lot of bug fixes, documentation and tests, see changelog.
The main author is u/raphlinus, I helped polish it.
Fuzzing is magic - Or how I found a panic in Rust's regex library
nibor.org/blog/fuzzing-is-magic---or-how-i-fo...Hi Rustaceans! I've recently written this:
for byte in buffer[..read].iter() {
result[*byte as usize] += 1;
}
And then changed it to this, which also works:
for &byte in buffer[..read].iter() {
result[byte as usize] += 1;
}
Is one of those preferred? If so, why?
The nice thing about the second one is that it shows that we're dealing with a reference right where the loop variable is defined. In the first one, that only becomes apparent when the variable is used.
On the other hand, if this were using iter_mut, then we'd need to use the first form in order to mutate the value using *byte = value.
