anderskaseorg

6 ms·

1.
by anderskaseorg 3mo ago
You have ignored the much larger space and time cost of constructing the range minimum query tree in the first place. Furthermore, nobody would arbitrarily cut off a problem at “billions” and then consider O(√billions) or O(∜billions) to be
2.
by anderskaseorg 6mo ago
The “next level” button takes you to the next level even if you haven’t solved that level’s prerequisites.
3.
by anderskaseorg 6mo ago
Right, the public was able to spend manual effort hand-auditing one specific tarball after it had already been singled out as suspicious for other reasons. In order for verification to effectively increase supply chain security, it needs to
4.
by anderskaseorg 6mo ago
The maintainer can verify the correspondence between source and release, but the public has been deprived of this verifiability. This matters. Consider the XZ Utils compromise where a malicious maintainer hid the line that triggers comp
5.
by anderskaseorg 6mo ago
The point of trusted publishing is supposed to be that the public can verifiably audit the exact source from which the published artifacts were generated. Breaking that chain via a private repo is a step backwards. https://docs.
6.
by anderskaseorg 1y ago
There is a well-defined reload point—it’s the `subsecond::call` wrapper around `tick()`. But the hypothetical design that you seem to have in mind where this doesn’t exist would not have a well-defined reload point, so it would need to be a
7.
by anderskaseorg 1y ago
Yes, uv has a standard permissive open source license (Apache-2.0 OR MIT): https://github.com/astral-sh/uv/?tab=readme-ov-file#license
8.
by anderskaseorg 2y ago
Of course (but that’s not relevant to the original scenario, where the programmer is hypothetically not aware that the read lock is still being held, let alone that they could manually upgrade it after changing to a different lock library).
9.
by anderskaseorg 2y ago
Yes, allowing this to execute would be very unsound: let lock = RwLock::new(Box::new(111)); let r: &i32 = &**lock.read().unwrap(); // points to 111 *lock.write().unwrap() = Box::new(222); // allocat
10.
by anderskaseorg 2y ago
Clippy already has an error for this pattern with Mutex. It should be trivial to extend it to cover RwLock. error: calling `Mutex::lock` inside the scope of another `Mutex::lock` causes a deadlock --> src/main.rs:5:5
11.
by anderskaseorg 2y ago
There are plenty of systems that sacrifice consistency even while the network is fully connected, in the name of performance—for example, DNS, or any system with a caching proxy server.
12.
by anderskaseorg 2y ago
You’re certainly allowed to make the client a more active participant in your consensus protocol, but then it needs to play by the same rules if you want the system to have guarantees. For example, you need to handle network partitions betw
13.
by anderskaseorg 2y ago
They’re doing a slow phase-out over a long time to try to avert a wave of bad publicity that threatens their browser monopoly, but that timeline has already started as of June. https://developer.chrome.com/docs/extensio
14.
by anderskaseorg 2y ago
The mechanism is a clever application of quines (self-reproducing programs), first explained in the classic lecture “Reflections on Trusting Trust” by Ken Thompson: https://dl.acm.org/doi/pdf/10.1145/358198.35
15.
by anderskaseorg 2y ago
When the term “undefined behavior” appears within the C standard, yes, that’s what it means. There is no way for another document to alter the meaning of “undefined behavior” as it appears within the C standard. When the term “undefined beh
16.
by anderskaseorg 2y ago
The jurisdictional status of .local and other standards-reserved special use domains is explained by RFC 6761 section 3: https://datatracker.ietf.org/doc/html/rfc6761#section-3 And ICANN is bound by the IETF/
17.
by anderskaseorg 2y ago
If a program’s behavior is undefined in one specification and defined in a second, then insofar as both specifications apply to it, that is defined behavior, not undefined behavior. That’s not an obscure property of terms of art and specifi
18.
by anderskaseorg 2y ago
It seems like you think I’m saying that all compilers are required to recognize all forms of UB and format your hard drive. Of course not; some UB in one specification may be defined in another more restrictive spec, some UB may be defined
19.
by anderskaseorg 2y ago
You may not like it, and it’s within your rights not to like it, but the reality is that compilers do treat UB this way , and it’s not “grossly dishonest FUD” to point out that this is the reality. Here’s a test case demonstrating that U
20.
by anderskaseorg 2y ago
Both (unsafe) Rust and LLVM have their own concepts of undefined behavior ( https://doc.rust-lang.org/reference/behavior-considered-unde... , https://llvm.org/docs/LangRef.html#undefined-values ), an
21.
by anderskaseorg 2y ago
Note that the “unsafe read beyond of death” trick is considered undefined behavior in the Rust and LLVM memory model, even if it’s allowed by the underlying hardware. Like any undefined behavior, compilers are allowed to assume it doesn’t h
22.
by anderskaseorg 2y ago
Here’s a message where you can see what this feature looks like (no login required): https://chat.zulip.org/#narrow/stream/101-design/topic/clock... (Note that the sender opts in to this with a specific
23.
by anderskaseorg 2y ago
Not yet, though there’s been some progress on developing this feature. You can upvote https://github.com/zulip/zulip/issues/23995 to help us prioritize it.
24.
by anderskaseorg 2y ago
We’d like to fix this! You can upvote https://github.com/zulip/zulip/issues/21881 to help us prioritize this feature.
25.
by anderskaseorg 2y ago
It worked in all major browsers until it was removed around 2017–2019. I personally used it, as part of MIT’s authentication systems.
26.
by anderskaseorg 2y ago
That will never happen, but RFC 6762 suggests some other options for private networks: .intranet, .internal, .private, .corp, .lan. https://datatracker.ietf.org/doc/html/rfc6762#appendix-G ICANN seems to be in the
27.
by anderskaseorg 3y ago
We could choose to design the language as I wrote where the constraint is implicitly present and variance consequently ought to preserve it, or as you wrote where it is not present at all and variance is unsound. But we want Rust to be sou
28.
by anderskaseorg 3y ago
https://github.com/rust-lang/rust/issues/25860#issuecomment-... “Similarly, the reason why niko's approach is not yet implemented is simply that getting the type system to a point where we even can imple
29.
by anderskaseorg 3y ago
In the language, fn foo<'a, 'b, T>(_: &'a &'b (), v: &'b T) -> &'a T { v } should be equivalent to fn foo<'a, 'b, T>(_: &'a &'b (), v: &
30.
by anderskaseorg 3y ago
Duplicate of https://news.ycombinator.com/item?id=39373327 .

More ›