Viewing profile — kobebrookskC3

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?

> 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 in…

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?

> simply by adding the formal verification that proves the safety which will work automatically "simply" and "formal verification" are usually oxymorons, never mind "automatically"…

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 p…

but without macros, how would you expose a safe interface? fn pin(x: T) -> Pin { ... } would move the value

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.

yes, but the code inside is unsafe. the pin macro is like a safe function.

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

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) a…

isn't that more like optimistic concurrency control?

> 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 …

> 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…

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

what would fil-rust do that miri doesn't?

> 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 …

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?

そんな暇ねぇよ

if it was in c, who knows how many memory corruption bugs would be found before they stumbled upon this...

they are memory safe

swift and rust?

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…

> 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…

stomping on in-bounds data might result in "nondeterminism", but bounded and not ub, which is unbounded.