kobebrookskC3

5 ms·

1.
by kobebrookskC3 4mo ago
china seems to be doing fine. what are you gonna do, tariff the country that makes all your stuff? 100% tariff on iphones and macbooks?
2.
by kobebrookskC3 5mo ago
> Constructing an invalid pointer in rust is UB no, it is dereferencing, not constructing, an invalid pointer, that is UB. there is even a safe function provided to construct an invalid but non-null pointer: ` https://doc.rust-
3.
by kobebrookskC3 5mo ago
is the fact that CHERI works better with C/C++ because of C/C++'s "anything goes" attitude, or simply that any hardware design that didn't support C/C++ well was discarded?
4.
by kobebrookskC3 6mo ago
> simply by adding the formal verification that proves the safety which will work automatically "simply" and "formal verification" are usually oxymorons, never mind "automatically"
5.
by kobebrookskC3 7mo ago
i was responding this claim > It would be perfectly possible to design a variant of Rust that gets you to 80-90% of Rust's usability, with the same safety, without macros. i then present an api that i think relies on macros to expos
6.
by kobebrookskC3 7mo ago
but without macros, how would you expose a safe interface? fn pin(x: T) -> Pin<&mut T> { ... } would move the value
7.
by kobebrookskC3 7mo ago
no, you just missed my point. expanding the implementation is not a safe abstraction. show me how you'd implement the functionality of the pin macro as a safe abstraction.
8.
by kobebrookskC3 7mo ago
yes, but the code inside is unsafe. the pin macro is like a safe function.
9.
by kobebrookskC3 7mo ago
the macro uses unsafe inside, so that's another instance of unsafe you'll need to check, whereas the pin macro is like a safe function
10.
by kobebrookskC3 7mo ago
how would you implement https://doc.rust-lang.org/stable/std/pin/macro.pin.html without macros? a macro is used to shadow the original variable so that you can't move it (safely) after you pin it
11.
by kobebrookskC3 8mo ago
isn't that more like optimistic concurrency control?
12.
by kobebrookskC3 10mo ago
> and you dont really have the choice - every society you could choose to be in, with the exception of yourself being a dictator, will have such people in ancient times, you could banish people from the village
13.
by kobebrookskC3 11mo ago
> engineers are expected to read the data sheet even if you know what the data sheet says, it's easier said than done, especially when the tool gives you basically no help. you are just praying people will magically just git gud.
14.
by kobebrookskC3 11mo ago
in my mind it would be doing what fil-c does for c to unsafe rust: a hypothetical memory safe implementation of unsafe rust using the same methods fil-c does e.g. gc
15.
by kobebrookskC3 11mo ago
what would fil-rust do that miri doesn't?
16.
by kobebrookskC3 11mo ago
> With non-deterministic tests I would always wonder if it's going to fail randomly after the code is already in production. if you didn't use property-based testing, what are the odds you would've thought of the case?
17.
by kobebrookskC3 11mo ago
it seems like the clean syntax makes the type checker's life harder and so performance is unacceptable. would you rather have clean syntax or acceptable compile times?
18.
by kobebrookskC3 11mo ago
そんな暇ねぇよ
19.
by kobebrookskC3 11mo ago
if it was in c, who knows how many memory corruption bugs would be found before they stumbled upon this...
20.
by kobebrookskC3 1y ago
they are memory safe
21.
by kobebrookskC3 1y ago
swift and rust?
22.
by kobebrookskC3 1y ago
in this example, aren't the scoping rules for c pretty much the same? what do the annotations for the tool look like? is the analysis local, in that it doesn't look into the bodies of other functions? if it is, surely you would ha
23.
by kobebrookskC3 1y ago
> there are products that offer memory-safety proofs for C what does the c checked by this tool look like? for an example like https://play.rust-lang.org/?version=stable&mode=debug&editio... , does the tool accep
24.
by kobebrookskC3 1y ago
stomping on in-bounds data might result in "nondeterminism", but bounded and not ub, which is unbounded.
25.
by kobebrookskC3 1y ago
because setting up and using anki is a pain? using and configuring anki is not intuitive. if you're just starting, you'll probably need to find a good premade vocab deck. once that's done, you'll need to make cards. maki
26.
by kobebrookskC3 1y ago
not if the app blocks screenshots
27.
by kobebrookskC3 1y ago
what happens when the legacy code is migrated to the new java, which is supposedly easier to upgrade post java 8? who will pay for long term support if upgrading is so easy?
28.
by kobebrookskC3 1y ago
wouldn't byte in rust be more like MaybeUninit<u8>, to account for uninit and pointer fragments?
29.
by kobebrookskC3 1y ago
the proof is so complicated it's hard to trust if it's only on paper. if we formalize it, it can be checked by a computer.
30.
by kobebrookskC3 1y ago
> Rust just survived by lying about the its safeties. strong claim. care to back it up?

More ›