kibwen

3 ms·

1.
by kibwen 5d ago
Previously: "Disney says man can't sue over wife's death because he agreed to Disney+ terms of service" https://www.nbcnews.com/news/us-news/disney-says-man-cant-su...
2.
by kibwen 6d ago
>> Why does ChatGPT need to know that? That should be illegal. > Something like it is basically a requirement if you want to see digital ads. So to summarize, yes, it should be illegal.
3.
by kibwen 6d ago
Comparing smartphones to antibiotics is somewhat ironic given that smartphone addiction is a disease, not a cure to one. There is no law of the universe that says that technology cannot create ills where previously there were none. I assure
4.
by kibwen 6d ago
The need to be instantly reachable at a moment's notice is a modern anxiety that we successfully lived without until the mass penetration of cell phones 20 years ago. Your spouse and children will manage without being able to text you
5.
by kibwen 6d ago
To imply that the only thing that qualifies a god is superhuman reasoning ability, rather than, say, omnipotence, or even omniscience (neither of which are anything any physical being will ever achieve, subject to the laws of this universe
6.
by kibwen 7d ago
I think there's some misconceptions floating around here regarding both Rust and Zig's const-evaluation philosophies. Rust is concerned about memory-safety, yes, but the only strict requirement for memory-safety when it comes to c
7.
by kibwen 7d ago
Arenas in Rust work very well with lifetimes. In fact arenas benefit greatly from lifetimes, because lifetimes allow them to uphold the usual Rust safety guarantees about preventing use-after-free. For example, here's the bumpalo crate
8.
by kibwen 8d ago
The Rust case was fixed back in 2021 via changes to LLVM, it didn't require waiting for the C++ standards body.
9.
by kibwen 8d ago
The reason for this is interesting. Loop constructs that you're guaranteed to enter have implications for control flow (in every language, not just Rust). It means that the following program is valid in Rust: let x; //
10.
by kibwen 8d ago
And unfortunately that argument would be incorrect, because not only is there a realistic chance of hitting this on embedded systems, the fact that LLVM baked this into its low-level semantics resulted in miscompilations in Rust for a time,
11.
by kibwen 9d ago
The story is about the fact that the Japanese government is reporting these figures, and what the Japanese government has tried to do and believes that it still needs to do in response to its own figures. That it then goes on to cast doubt
12.
by kibwen 10d ago
For long-term backups you want offline cold storage in an underground facility in a friendly jurisdiction, not a datacenter.
13.
by kibwen 10d ago
According to the documentation there are four things: 4) naming things 5) keeping the documentation up-to-date
14.
by kibwen 10d ago
> most games will run on future hardware. I'm starting to get uncertain about how much longer there will even exist future Playstation hardware. Apple and Google phones have devoured the casual/mobile gaming market and as tha
15.
by kibwen 11d ago
Behold, the real bull case for SpaceX: not space-based datacenters, colonizing Mars, or asteroid mining, but the thorough militarization of Earth's orbit by the US.
16.
by kibwen 13d ago
But `panic!()` is just a macro invocation that needs to expand to something, and the question here is what that something ought to be in order to produce a valid program. Currently it expands to this: https://github.com/rust
17.
by kibwen 13d ago
I wouldn't say they got it wrong exactly. Uninhabited types aren't equivalent to unit types, but in terms of Rust they're both classified as zero-size, and I suspect they were just pointing out that Rust has optimized and spe
18.
by kibwen 14d ago
None of this has anything bad to say about coercion or fallback, it's a consequence of the fact that Rust is an expression-oriented language which had expressions (like `loop {}`) which logically evaluated to the never type when in ret
19.
by kibwen 14d ago
And then once you have `fn foo<T>() -> T`, what do you write in the body that allows it to typecheck?
20.
by kibwen 14d ago
I'm unclear what this is implying, but in Rust the never type is uninhabited. https://doc.rust-lang.org/reference/items/enumerations.html#...
21.
by kibwen 14d ago
Let's avoid using the term "subtyping", which as you say is irrelevant here. The reason you need diverging functions to satisfy arbitrary type obligations (i.e. to coerce to any other type) is because otherwise anything as si
22.
by kibwen 14d ago
Do you have some specific coercion in mind that you want to forbid? Unlike C, Rust is extremely tame when it comes to coercions. Forbidding coercions in general in Rust code doesn't really make sense, and I can't think of any that
23.
by kibwen 14d ago
The exclamation point is also used both as the C-style negation operator and as the identifier suffix that indicates macro invocations, so it was unlikely that it would have been used for any new feature. As my sibling comment notes, this s
24.
by kibwen 14d ago
> Is it obvious to rust developers that "!" would be the never type? Prior to this change most Rust developers would never have cause to ever use `!` for any reason. The only stable way to do so would be to specify the quote-
25.
by kibwen 14d ago
The compiler does everything that the language spec allows it to get away with. The language spec itself is a communication protocol between users and compilers, and that includes the definition of the abstract machine.
26.
by kibwen 15d ago
There will be no curiosity, no enjoyment of the process of life. All competing pleasures will be destroyed. But always—do not forget this, timcobb—always there will be the intoxication of power, constantly increasing and constantly growing
27.
by kibwen 15d ago
Why's it hard to believe? Look around you at how belligerently foolish, irrational, inefficient, dysfunctional, and confidently wrong every large organization acts. Marketing departments confidently report that their marketing campaign
28.
by kibwen 15d ago
"ChatGPT, use the stylometry that you've developed via hoovering up the history of every internet post ever written to divine the true identity of Satoshi and dispatch men with $5 wrenches to his home address."
29.
by kibwen 16d ago
Rust's raison d'être is to improve the confidence of the security-critical parts of your system. You don't need to rewrite all 30M lines of code to benefit from it, you just need to identify the 1% of your codebase with the g
30.
by kibwen 17d ago
"More painful" is just being used to mean "explicit", and being explicit rather than implicit about intention is absolutely a PL theory concept, e.g. the whole difference between static and dynamic typing, or strong typi

More ›