nmsmith

6 ms·

1.
by nmsmith 1y ago
You mean the positive impact of consuming statins. Consuming statins coincides with lower LDL so I can imagine people conflating the two variables. I'm sure taking statins also has other effects on the body.
2.
by nmsmith 1y ago
Yes, functions can return non-owning references. However, those references do not "borrow" their target, in the sense that they lock others out. That is the Rust model, and OP does a great job covering its limitations. So, with th
3.
by nmsmith 1y ago
Hardware-based instruction reordering always preserves the behaviour of the original program. (Assuming the original program is valid.) For example, an Intel CPU won't reorder `x += 1` and `x *= 2`.
4.
by nmsmith 1y ago
Yep, that's an accurate summary! The model still features a form of "borrowing", it just happens at the granularity of groups. I wrote a more detailed answer here: https://news.ycombinator.com/item?id=45057636
5.
by nmsmith 1y ago
The "Group Borrowing" concept that we're discussing still imposes aliasing restrictions to prevent unsynchronized concurrent access, and also to prevent "unplanned" aliasing. For example, for the duration of a funct
6.
by nmsmith 1y ago
Hi there, I am the Nick whose design we're discussing. You raise some valid points: the blog post enumerates some limitations with Rust's model, but my design (as written) only resolves a subset of those limitations. We probably s
7.
by nmsmith 2y ago
Do you remember what language that was? Or at least, how I'd find it? I'd be interested in checking it out.
8.
by nmsmith 3y ago
> building a tree in Rust will do a lot of reference counting This isn't true in most cases. If every subtree is only referenced by its (unique) parent, then you can use a standard Rust "Box", which means that during compi
9.
by nmsmith 6y ago
The multidimensional version definitely looks exciting! Do you have any benchmarks for it yet? And will you be publishing a paper on it?