Plugin is likely lewis6991/gitsigns.nvim
asonix
joined 4 years ago
i might try
let res = collection.into_iter().map(|item| item.fallible_operation()).fold(Ok(Vec::new()), |acc, res| {
match (acc, res) {
(Ok(mut vec), Ok(item)) => {
vec.push(item);
Ok(vec)
(Err(mut vec), Err(error)) => {
vec.push(error);
Err(vec)
}
(Ok(_), Err(error)) => Err(vec![error]),
_ => acc,
}
});
Maybe expand it with
pub trait Evert<T, E> {
fn evert(self) -> Result<Vec<T>, Vec<E>>;
}
impl<I, T, E> Evert<T, E> for I
where
I: IntoIterator<Item = Result<T, E>>,
{
fn evert(self) -> Result<Vec<T>, Vec<E>> {
self.into_iter().fold(/* implementation from above */)
}
}
fn main() {
let result = vec![Ok(1), Err(3), Ok(4), Err(8)].evert();
assert_eq!(result, Err(vec![3, 8]));
}
With these examples I think the correlation is a little loose. Dr Lutchmedial died two weeks after his third shot. Claiming the vaccine was a direct cause when the only available evidence is a two week timespan is weak.
The other example provided doesn't demonstrate harm caused by a vaccine. It sucks that a deadly virus is deadly, and it sucks that the vaccine didn't help in this case. It's not a good argument against getting a vaccine.
I'm a sponsor on github for spacejam (github user) and elementary OS, and I'm a patron of Hector Martin on patreon.
First, it doesn't take an array as input, it takes a slice as input. You can turn a Vec<&str> into a slice &[&str] by borrowing it.
Second, the human-sort crate's api is bad, because rarely to people have Vec<&str> or &[str] and there's no way to produce a Vec<&str> from a Vec<String> without creating a new vector that borrows from the first.
let mut strs = Vec::new();
for s in strings.iter() {
strs.push(s);
}
human_sort::sort(&mut strs);
What human-sort should have done was accept &[T] where T: Deref<Target = str> which would allow passing a Vec of String or a Vec of &str.
Feel free to open a PR against human-sort, but it looks like it hasn't been updated in a couple years so it might not be maintained anymore
Pawoo is a mastodon server run by the same company that owns pixiv. They're using the default mastodon description but have also deliberately added tracking because they're a company that doesn't care about privacy.
I dont really know what point this post is trying to make. There are other mastodon servers you can join that wont track your activity.
It also has .flush() and .flush_async() to flush inline with your application if you need that
Sled is my go-to key value store in Rust. It flushes to disk every 500ms by default iirc
I love writing rust and I've done all my personal projects for the last 4 or 5 years in it, but I dont think it's a good idea for other existing languages to adopt more of Rust's features.
Languages like Elixir or Lisp are so different it doesn't make any sense to adopt Rust semantics or syntax, and anything with a garbage collector, Go included, doesn't need to care about ownership, borrowing, or lifetimes (besides the usual passing references being cheaper than passing whole objects).
Languages like C or C++ can definitely be replaced in many cases with Rust, but I dont think making them more like rust is a wise decision. Adopting something like a borrow checker in c or c++ completely changes the language in a way thats not only backwards incompatible, but also probably not welcome by developers already working in those languages.
All this to say: I'd prefer more people to work in rust than to alter other languages to be more like rust, but I also think there are a number of other languages worth learning and working in. To a large extent, choosing a language is about taste.
oh I forgot to mention pict-rs is now nicely instrumented with the tracing framework and can export spans to OTLP collectors if the opentelemetry_url configuration option is set. It supports reading OpenTelemetry span information out of HTTP requests to enable tracing requests through the calling application to pict-rs and back. This is incredibly helpful for debugging.
Since lemmy is not instrumented (yet) with tracing, the benefit to lemmy admins and developers is not much, but this prepares for a future when lemmy is instrumented.
This also changes how pict-rs logs look. Hopefully admins and developers can glean more information from pict-rs logging now, especially in the event of an error.
view more: next ›
Lemmy and pict-rs support optionally exporting opentelemetry spans, and setting up Jaeger to capture those is a nice way to manage traces without shipping data to third parties