Viewing profile — workingjubilee
workingjubilee
HN member- Joined
- Tue, Apr 11, 2023, 1:59 AM UTC
- HN karma
- 49
- Public activity
- 21 items
- HN profile
- View on Hacker News ↗
About workingjubilee
No profile information was provided.
Recent public activity
-
comment
Comment #42942572
The other procedural languages are also not mystically secure from soundness problems, people just fuzz them less.
-
comment
Comment #42489325
I'm not based in China, bro. You're the one who went around accusing random people of being advanced persistent threat actors, and now you can't even keep your story straight. Do n…
-
comment
Comment #41179212
The "small string optimization" makes the strings harder to manipulate with `unsafe` code. However, being easy to manipulate with `unsafe` code is in fact a priority for most std t…
-
comment
Comment #40757136
I don't usually express my frustration by shouting at a pile of HTML but this one had me going "LEMME LOOK!"
-
comment
Comment #40572635
struggle sessions usually involve public torture or executions. it's laughable to compare "being mildly inconvenienced" with that.
-
comment
Comment #40249767
what would "stabilize" mean when the opsem model that miri obeys continues to change?
-
comment
Comment #40141139
yeah, g-d forbid that any routine busywork gets automated by software, otherwise all those lines of code might actually have a point!
-
comment
Comment #40083874
The Rust calling convention is actually defined as unstable, so 1.79 is allowed to have a different calling convention than 1.80 and so on. I don't think designing one for the long…
-
comment
Comment #40083724
Allowing developer control over calling conventions is also simultaneous with disallowing optimization in the case that Function A calls Function B calls Function C calls Function …
-
comment
Comment #40083667
Your experience is not perfectly transferable. JITs have it easy on this because they've already gathered a wealth of information about the actually-executing-on CPU by the time th…
-
comment
Comment #39034201
This is a frankly ridiculous assertion given LKML's notoriously toxic history. Part of the problem is that overly-entitled maintainers can be as equally dangerous to actual progres…
-
comment
Comment #37924851
Nice.
-
comment
Comment #37830261
aw geez, now we have to compile docs, too?!
-
comment
Comment #37827341
Eliminating "custom workflows" seems like rather the point of such an extension.
-
comment
Comment #37782542
Have you ever heard of "CMPXCHG8B"?
-
comment
Comment #37549043
You have not described a mechanism or API by which the compiler or programmer could enforce that only Leak types are on the stack and that a longjmp will not traverse `!Leak` types…
-
comment
Comment #37515205
It can be the case that people didn't feel that unions were a net positive from the 1960s~2000s and now, starting from somewhere in the late 2010s, have begun reconsidering whether…
-
comment
Comment #37214543
My remark was an observation based on the obvious public resentment, rather than necessarily an exhortation to do so. I promise you, I will not be so cagey and ambiguous when I act…
-
comment
Comment #36962191
The answer to that is simple: We do. We try to catch things before public release. We run UNSPEAKABLE amounts of regression tests. We ask people to test unstable things. Almost no …
-
comment
Comment #35519876
The rustc driver for trusted PL/Rust prevents using the subset of the Rust language required to trigger those issues. Most of them are things that would have a hard time traversing…
-
comment
Comment #35519811
It's just the name of the repo: the actual target is ${arch}-postgres-linux-gnu.