Just apply Betteridge's law of headlines.
HN user
CUViper
[ my public key: https://keybase.io/cuviper; my proof: https://keybase.io/cuviper/sigs/cvbDtsN5sZS8LXYsp5qx5SgsxrpkGzzKem_yMPLGvFc ]
Synergy still exists, but barrier has forked again to input-leap.
Intel's compilers are now based on LLVM too.
Whenever I hit the age gate in the Steam store, I just bump the year to continue, so January 1st it is!
Even if a pointer was guaranteed correct at the time of creation, it can't be known safe to dereference in the future unless you put a lifetime on it, and then it's just a reference.
Best practice is to resolve them early now: https://www.redhat.com/en/blog/hardening-elf-binaries-using-...
The crescent moon is often depicted with the dark part transparent too, e.g. with stars in that space.
Rust is backwards compatible when you stick to stable features, but the kernel uses unstable features that can and do incur breaking changes.
There was also https://github.com/jameysharp/corrode
Then extrapolate "random guy trying to follow dtolnay's lead."
RV64GC is mentioned here: https://wiki.debian.org/RISC-V#Hardware_baseline_and_ABI_cho...
Fedora 38 removed the filter: https://fedoraproject.org/wiki/Changes/UnfilteredFlathub
In the conclusion:
We fully expect to continue offering the Zulip Cloud Free plan indefinitely,
ntcompatible.com was a great resource for this - I spent a lot of time in those forums.
If pure red is at 0° hue, and orange at 30°, then that engineering value at 3° is much closer to red. The other two at 18° and 19° better fit the reddish-orange description, still more orange than red, while safety orange is up at 28°.
Parenting is like being an NPC in that magic of childhood. You get to live through that again, just not as the main character. I imagine that starts again as a grandparent, but I'm not there yet.
Probably the addition of `thread::scope`.
There are a few where it does win though -- I wonder what characteristics favor VisionFive in those?
Why not offer 1 million for the signed contract?
If I were offered that out of the blue, I'd be wondering what true value I'm holding to make that signature so important.
Base16 does that: https://github.com/chriskempson/base16
That doesn't work for multiplication -- e.g. in 8-bit, 20 * 20 wraps to 144.
It's a little ambiguous, but the word before is important -- "Sampling certain workloads with IBS" -- so that "with" clause is talking about the sampling method, not the workload style.
Yes -- they dropped the "Mega" in 1999.
That's experimental syntax that means something like "maybe const" -- https://github.com/rust-lang/rust/issues/67792
Here's 32 boards: https://duotrigordle.com/
Throw those into Copilot for filmmakers and away you go!
In the LWN comments, mjw said that Valgrind just forces an ENOSYS error.
It can be applied more generally. If you're focusing on improving the performance of something that only takes 10% of your time, then the other 90% will still dominate.
Note that "tidy" only checks code in the rust-lang/rust repo, not all Rust.