Viewing profile — Gankra
Gankra
HN member- Joined
- Mon, Jan 24, 2022, 8:41 PM UTC
- HN karma
- 407
- Public activity
- 27 items
- HN profile
- View on Hacker News ↗
About Gankra
No profile information was provided.
Recent public activity
-
comment
Comment #34618509
Do you mean this kind of dep? https://rust-lang.github.io/rfcs/3028-cargo-binary-dependenc... That's an interesting thought, I'm not sure I've ever seen someone employ that as a pa…
-
comment
Comment #34617962
Just to elaborate on this a bit: as discussed in the Concepts section of the docs[0] the core of cargo-dist absolutely supports workspaces with multiple binaries, and will chunk th…
-
comment
Comment #34617750
The "way-too-quickstart" is the minimal example: https://github.com/axodotdev/cargo-dist#way-too-quick-start A key feature of cargo-dist is that cargo dist init --ci=github should …
-
comment
Comment #34617364
Correction on this someone else sent me: The check of interest is for a Mark Of The Web[0] flag that Windows includes in file system metadata. The builtin unzipping utility just fa…
-
comment
Comment #34575509
They are exactly the same except for when they're not. (On 64-bit) Rust very naively has two 64-bit integers for the strong and weak count, Swift packs them into only one. Swift al…
-
comment
Comment #34574806
The biggest problem is that if you have a big """zero-cost-abstraction""" blob like iterator adaptors -- `Map >>>` -- and a single drop of Resilient Type is in there (i.e. MyType i…
-
comment
Comment #34574695
The greatest trick Swift's developers ever performed was convincing the world that it wasn't just a better UX layer on top of COM
-
comment
Comment #33823602
No the claim is always that Rust "must" be slower than C/C++ because it has pervasive bounds checking for array indexing. Then people insist on wanting to replace every x[i] in pro…
-
comment
Comment #33822787
there's almost no bounds checking in rust code before the optimizer even looks at it because we use iterators and not goofy manually indexed for loops that are begging you to make …
-
comment
Comment #33350606
The null pointer optimization is documented in many places, here's one official instance I published in 2015 : https://doc.rust-lang.org/nomicon/repr-rust.html There are many rando…
-
comment
Comment #33350462
I am one of the people who has written a lot of Rust's docs, including one of the early attempts at "specifying" details of the language: the Rustonomicon. Rust's documentation is …
-
comment
Comment #31854648
Going into this project I was very high on the idea of "different architectures should get completely independent stackwalker backend implementations" (although they call in to som…
-
comment
Comment #31745067
That article is about the client-side (generating the minidump for a crashed process) to this article's server-side (processing/analyzing the minidump).
-
comment
Comment #31743299
Yeah computing backtraces in a crashreporter is extremely similar to a debugger in that you need a lot of fudge-factor heuristics and fallback modes for known toolchain bugs or com…
-
comment
Comment #31741964
No we removed many random crashes that the C++ code had. You cannot "simply" discard a crash report if something is slightly off because then you would discard most crash reports. …
-
comment
Comment #31741387
Extra shoutouts to the folks at Sentry who also flipped rust-minidump on as their default backend and had to deal with way more exotic issues than I did (and fixed them!) because a…
-
comment
Comment #30937796
My understanding is that CHERI just tells you to eat your vegetables and properly maintains a chain of custody from like bootloader to kernel to subsystems to drivers, so that anyo…
-
comment
Comment #30937552
Rust is no more unsound than C/C++/Swift here. It basically works but that's a really frustrating answer for anyone who cares about validation/sanitizers/optimization/docs. It's ju…
-
comment
Comment #30936194
Iain and I previously discussed this a bit, so just to add context: WebKit is already ported to CHERI BSD, so there are definitely solutions to the kinds of hax that JIT VMs like t…
-
comment
Comment #30936136
I already designed several new convenience methods for making this kind of thing simple and the PR to rust-lang is already open :)
-
comment
Comment #30936098
Yeah "it's actually xoring array indices" is the standard solution Or you can go Deep on memory models and try to apply Ralf's Xor Provenance Hack and claim that, well, provenance …
-
comment
Comment #30743591
~ is not -> ptr->field in C is (*ptr).field, at which point you are in whatever C's equivalent of a "place (lvalue) expression" is. This creates a weird discontinuity where you -> …
-
comment
Comment #30740590
No, as my article notes, because C has a dozen slightly different definitions for "integers that are basically pointers" they were able to keep size_t 64-bit and make intptr_t into…
-
comment
Comment #30740436
hmm i've always just mentally modelled TLS as "yeah the OS slaps a pointer to an array in this one register". but i guess the difference between "pointer to an array" and "a segmen…
-
comment
Comment #30337667
The fact that there are many different pixel layouts on phones is kinda irrelevant since they've largely all converged on retina resolutions for their viewing distance, making subp…