3 ms·

You're ignoring the case of a list being densely packed and embedded inside another data structure. If you bloat a data structure with a useless machine word, t

You're ignoring the case of a list being densely packed and embedded inside another data structure. If you bloat a data structure with a useless machine word, there are all sorts of ways for that machine word to hurt the resulting program, and you can't just handwave that away. The Linux kernel is made by people who spend weeks to shave one bit off the size of a data structure. Do you really think they'd respond positively to your saying they don't need to do that? You really need to stop assuming what kind of computers other people are programming The larger point here is you don't get to decide whether other people's use cases are legitimate. Either Rust gives you complete control of the machine or it does not. It does not, not in safe mode, but Rust people keep doing this annoying motte and bailey thing about it.

volta83 5y ago
> You're ignoring the case of a list being densely packed and embedded inside another data structure. No, I am not. This conversation is exclusively about non-intrusive doubly-linked lists. If you want to have a conversation about intrusive doubly-linked lists we can have it, but it is a very different data-structure. > You really need to stop assuming what kind of computers other people are programming Every week I touch x86, arm, ppc64, riscv and gpu assembly. I write code for apps daily that run from 16-bit micro controllers to the largest super computers in the world, going through phones, desktops, cloud, etc. I am not assuming what others are programming, but rather talking about what I program for, which include most hardware that anyone can buy today, and quite a bit of hardware that almost no one can even buy, as well as hardware that's not for sale.
arcticbull 5y ago
This conversation started where folks were talking about where to begin learning Rust. Beginning by learning unsafe{} implementations of a doubly-linked list to save 1-4% of the performance isn't where I would recommend anyone begin learning. If they do need to shave a single bit off, they can do that, that's a neat feature too.

volta83 5y ago

> You're ignoring the case of a list being densely packed and embedded inside another data structure. No, I am not. This conversation is exclusively about non-intrusive doubly-linked lists. If you want to have a conversation about intrusive doubly-linked lists we can have it, but it is a very different data-structure. > You really need to stop assuming what kind of computers other people are programming Every week I touch x86, arm, ppc64, riscv and gpu assembly. I write code for apps daily that run from 16-bit micro controllers to the largest super computers in the world, going through phones, desktops, cloud, etc. I am not assuming what others are programming, but rather talking about what I program for, which include most hardware that anyone can buy today, and quite a bit of hardware that almost no one can even buy, as well as hardware that's not for sale.

arcticbull 5y ago

This conversation started where folks were talking about where to begin learning Rust. Beginning by learning unsafe{} implementations of a doubly-linked list to save 1-4% of the performance isn't where I would recommend anyone begin learning. If they do need to shave a single bit off, they can do that, that's a neat feature too.