voorwerpjes

5 ms·

1.
by voorwerpjes 4y ago
I like how this highlights the pitfalls of using `as` to cast between types. The article says to prefer using `try_into()` instead of `as`, which is a good suggestion when available, but `as` lets you cast between floats and ints, while `tr
2.
by voorwerpjes 4y ago
These types of GRBs are caused by the death of massive stars with low metallicity, not active galactic nuclei. There absolutely could be a GRB inside of the milky way galaxy pointed at us, but it is very unlikely.
3.
by voorwerpjes 4y ago
Very cool! I don't understand the motivation about lifetimes in sync rust not being able to be arbitrary. I'm also confused because most of the time went you want to send data around in a async context you wrap it in `arc`, which
4.
by voorwerpjes 4y ago
I agree with you but just for completeness the rust equivalent is unsafe { *ten_things.get_unchecked_mut(11) = blah } Which goes to show that usually the unsafe methods are more verbose and annoying to deal with. Devs won't reach for
5.
by voorwerpjes 4y ago
This would be really cool! you should open up a RFC for it.
6.
by voorwerpjes 4y ago
Leaks can happen in rust. The guarantee safe rust makes is that memory leaks cannot result in undefined behavior.
7.
by voorwerpjes 4y ago
There are similar issues in Rust to the one Hickey talks about in Java, in terms of cognitive overload and difficulty in a human parsing the program. However, I've found rust largely avoids issues with a bunch of different classes and
8.
by voorwerpjes 5y ago
Former academic scientist, now software engineer. I think this article misses the point that rarely in science is the code the actual product/deliverable. The way a scientific code should be judged is it performant enough to answer my
9.
by voorwerpjes 5y ago
For a job interview I did the same parallelization of a`isPrime` in Rust, and it the basically as simple as the one for Julia, replacing a call of `into_iter()` with `into_par_iter()`. I also show the strong scaling relationship, which i wi