artikae

7 ms·

1.
by artikae 5mo ago
Goodhart's Law vs the Turing Test! Can our humans accurately evaluate intelligence, or will they be fooled by fakes? Live this Sunday!
2.
by artikae 11mo ago
Yea, but, this is Rust. How is a moving GC supposed to handle an untagged union? Or a person who uses the now-stable provenance api to read/write pointer bits to/from disk.
3.
by artikae 11mo ago
A Gc<T> that can't give you a pointer inside seems almost unusable in the context of Rust. Pointers are not a narrow use case; references are pointers. Rust APIs are largely built around references. If you were to put a Vec<
4.
by artikae 1y ago
> those only apply to arrays of primitives I guess you've not written much python, or just not used any custom types in lists if you have. class Thing: def __init__(self, a, b): self.a = a; self.b = b
5.
by artikae 1y ago
Are you blind or using Orca to interact with your computer? If the answer is no, then your recent experience with Debian is not particularly relevant to what the article is talking about, since you obviously wouldn't have run in to any
6.
by artikae 1y ago
What about this: https://godbolt.org/z/xP9xG3Ee3 Here the compiler "register allocates" i for some reads but not for others. i gets stack allocated, but some uses of it act as though they were register alloca
7.
by artikae 2y ago
assoc-in reminds me a lot of lenses in Haskell. I figure you could probably implement something like it using them. This is what I came up with: import Control.Lens baseLens --> nextIndex = baseLens . ix nextIndex assocIn structu
8.
by artikae 2y ago
All it takes for something to be replaced is something that does the job better. You can only really apply your definition in hindsight, after something has stood the test of time. You can't tell the difference between sails and wheels
9.
by artikae 2y ago
The first line is already UB. `assume_init` requires the contents to be initialized, hence the name.