If you know what I meant, then what's up with your snarky comment about "So much for effectively disabling stuff"? In your playground link, you did effectively disable the borrow checker in safe parts of the code. Next thing you're moving the goalpost, now it's not about external, static analysis tools: "run this with UBSAN, ASAN, and other C tools". I don't think you're arguing in good faith here. Goodbye.
Please try to interpret comments in the context of the discussion, not floating freely in a vacuum. The context of the discussion is the Bun port's excessive use of unreviewed unsafe blocks. unsafe in Rust can easily be misused to create Undefined Behavior, which renders any safety guarantees otherwise ensured by Rust's borrow checker invalid.
> Does bun actually do anything insane like that in its unsafe blocks?
Who knows? At 10k unreviewed uses of unsafe, I'd guess there are quite a few incorrect ones. LLMs don't produce perfect code (neither do humans), so there's a high probability that at least some of those create UB.
fn main() {
let mut x = 1_u32;
let reference_a = &mut x;
let reference_b = trust_me_bro(reference_a);
*reference_b = 2; -- Whoops
println!("reference_a: {reference_a} reference_b: {reference_b}");
}
After the call to trust_me_bro, two aliasing, mutable references exist simultaneously. This would usually be prevented by the borrow checker, but the unsafe code has effectively disabled it.
True, but unsafe let's you conjure up any lifetime you want, or any lifetime necessary to satisfy the lifetime requirements in safe code. If you generously sprinkle pointer dereferences in unsafe code, you effectively disable the protection provided by the borrow checker – including in safe code – until you've checked and verified the correctness of all unsafe blocks.
Those systems you're alluding to received ungodly amounts of work and resources, vastly more than most projects can ever hope for, and yet they're still full of holes and security exploits. You're unwittingly making a great argument against using C, C++ – or Zig.
Are you sure about "rms types" specifically? Stallman is very ineffective in his proselytization, owing to his complete refusal of any kind of compromise or concession to dissenting positions. This stance may keep your soul pure and righteous, but it won't bring you one millimeter closer to your objectives.
The human brain hasn't solved NP-hardness, either. We make it work using heuristics and automation tools, which in turn use heuristics themselves. I see no reason why AI wouldn't be able to take the same approach.
Solving the halting problem is neither necessary nor sufficient to prevent DoS attacks.
It isn't necessary, because settings timeouts or other resource restrictions works way better to prevent DoS.
It isn't sufficient, because even if you can prove that a program will halt at some point, this alone doesn't tell you how long it will take. What good does it do to know that the program will run for 10 years before it halts? By that time, service will already have been denied. Even turning hash table lookups from O(1) to O(n) (still very much terminating!) can result in a DoS.
> probably is somewhat of a loss leader for small-batch users
Wrong. AMD/Xilinx doesn't sell devices directly to customers, they sell them to distributors in huge quantities. Those distributors then sell them to "small-batch users", and they're not involved with AMD/Xilinx free-tier software at all.
> they’re running at around -10% profit on small sales to try and drive subscription revenue multipliers
I think you're conflating qualia with free will. These are very different concepts, and the experience of qualia has nothing at all to do with "violating causality".
> So there should be no reason we cannot reduce these phenomena to actual quantifiable and there for Computable elements.
As long as we have practically no idea how qualia arise, or even what exactly they are, your claim has no base to stand on.
No, there is at least one other option, which is that consciousness [1] is a phenomenon that we can't replicate in non-biological brains [2], but from which the existence of a "God"-like being, as the term is understood by major religions, still doesn't follow.
[1] Or "qualia", to be precise.
[2] For example, the existence of qualia might require certain carbon-based structures which aren't present in silicon-based devices.
And yet another "AI doesn't work" comment without any meaningful information. What were your exact prompts? What was the output?
This is like a user of conventional software complaining that "it crashes", without a single bit of detail, like what they did before the crash, if there was any error message, whether the program froze or completely disappeared, etc.
> We could probably slash gas prices by banning oil exports, thus removing domestic oil supply from global market pricing (barring smuggling).
To my understanding, you couldn't do this, no. The US is a net oil exporter, but many of its refineries are tuned for processing oil with a chemical composition that isn't found in the US, or not found in sufficient quantity. So the US has to both import and export oil, it can't just replace imports with exports.
> ironically because he thought it would avoid making him look weak and incompetent
Trump is what a weak man imagines a strong man to be like. Just look at his official portrait [1], trying to look tough and dangerous. Compare that to Dwight D. Eisenhower's portrait [2], a man who commanded entire armies in the largest war in human history.
Oil is a globally priced commodity. This means that downstream consumers of oil in the US will be just as affected by rising prices as European consumers. US producers of oil will benefit, though.
.jpg){kind=link}
(3).jpg){kind=link}
You're just splitting hairs and trying to weasel around the fact that yes, you really can create any lifetime you want using unsafe.
> Not sure what you meant by this example since it doesn't compile.
That's because the crappy HN formatting ate some of the characters. Here's the original version:
https://play.rust-lang.org/?version=stable&mode=debug&editio...
> What you probably meant is […]
If you know what I meant, then what's up with your snarky comment about "So much for effectively disabling stuff"? In your playground link, you did effectively disable the borrow checker in safe parts of the code. Next thing you're moving the goalpost, now it's not about external, static analysis tools: "run this with UBSAN, ASAN, and other C tools". I don't think you're arguing in good faith here. Goodbye.