So, to be clear, you pulled your children out of public school because students were being educated to accept other people who do not adhere to their own set of religious and cultural beliefs, in a country founded on freedom of religion?
And now instead of learning science in a lab and socializing, they are forced to maintain your farm?
You're forgetting an important distinction: Freedom of religion amongst various Christian denominations. Failure to recognize this as a historical fact leads to back to the original point of public education being a morality platform and not an objective educative platform.
It's pretty easy to do at runtime without weak pointers, people who write rust are just allergic to reference counting. Which is absurd, because most programmer use RC values thousands of times every day without even thinking about it. It's really this easy: https://pastebin.com/SAeKG7Sw
works, but you have to manage your own teardown of the list. If you use Weak, releasing the strong reference to the head of the list tears down the whole list.
One of my work computers died and I hadn't checked the CPU market in years. Rode home that night in a taxi with a Ryzen 1700x completely stoked that AMD was back in the game.
If anyone thinks competition isn't good for the market or that also-rans don't have enough of an effect, just take note. Intel is a cautionary tale. I do agree we would have gotten where we are faster with more viable competitors.
M4 is neat. I won't be shocked if x86 finally gives up the ghost as Intel decides playing in Risc V or ARM space is their only hope to get back into an up-cycle. AMD has wanted to do heterogeneous stuff for years. Risc V might be the way.
One thing I'm finding is that compilers are actually leaving a ton on the table for AMD chips, so I think this is an area where AMD and all of the users, from SMEs on down, can benefit tremendously from cooperatively financing the necessary software to make it happen.
I have retreated into only accepting small snippets from it. Asking it to write print functions, that sort of thing, or a specific loop that I hand-review. For the same reason.
The issue is most developers do not bother to write any, and the ones that are written are most-often vapid typing failures ("these`int`s cannot be negative" should be handled by a type). I studied this field in grad school, and the entire problem almost always devolves into convincing developers to engage with the system.
I find that is the case with almost all methodologies for software quality improvement. If you can't enforce that people follow it then it's not worth anything.
This sort of manual has since been gamified by Zachtronics, and I think it is genuinely a better alternative. If you are trying to pick up the basics of programming assembly and are already committed to use a "fake" language, why not enjoy the experience as a video game?
And it does not help that this page starts with a dick joke.
Because Zachtronics games are constrained in ways that real ISAs aren't for the sake of good puzzle gameplay. It's about as meaningful as trying to learn to be an infantryman by playing Doom.
I came to hacker news to take a break from a TIS-100 session, and read this comment. It frustrates me that the TIS-100 machine does not use real bytes. I have been working on puzzles that require division, and am sore that there is no right-shift.
And like everything else in Rust, it will forever live in the "unstable" pile of features that are required to use the language without standing on your head (looking at you, pattern matching through boxes).
And now instead of learning science in a lab and socializing, they are forced to maintain your farm?
What an good job you are doing!