o hai mark
@lemmy.kde.social
o hai mark
I was vaguely aware that some ancient architectures had weird byte widths, but I did not know about this. Pretty interesting.
This paper cannot succeed without mentioning the PDP-10 (though noting that PDP-11 has 8-bit bytes), and the fact that some DSPs have 24-bit or 32-bit words treated as "bytes." These architectures made sense in their era, where word sizes varied and the notion of a byte wasn’t standardized. Today, nearly every general-purpose and embedded system adheres to the 8-bit byte model. The question isn’t whether there are still architectures where bytes aren’t 8-bits (there are!) but whether these care about modern C++... and whether modern C++ cares about them.
I've been keeping an eye on the multicommunity issue and that getting merged was a nice notification.
Thinking of further use cases, maybe a multicommunity could be used as an "Instance curated" option in addition to All/Local/etc. Because frontpages of topic-specific and regional instances seem to all be dominated by us politics.
As much as I wish votes could be private, obfuscating them would make troll instances harder to notice. I think I hate it the most that the current model gives the illusion of being private, when it isn't.
The file is named Cargo.toml. Whatever dependencies you add to there are automatically downloaded by Cargo. You can manage them with cargo add and cargo remove.
cargo install is not the same thing. That installs binaries. I last installed cargo-release to automate the annoying part of managing git tags and crate version number.
thanks for using Leebra!
go to feed...