why isn't it inconsistent to allow creation of a record with missing components but to deny creation of a stack frame with missing components
good
yeah the actual titleholder to those is seattle
rustup is available in your package manager's repository
?
> Rust must stabilize its ABI if it seeks to be a useful systems language. ? no it mustn't. what's the c++ abi
> Having multiple implementations is a sign of a healthy programming language this is frequently taken as axiomatic but there's no actual support for it in reality. there are plenty of healthy single-implementation…
why not
every time this comes up i just have to ask - what do you think a language standard is or does - what languages with standards do you think standardization has helped (this is a trick question! do not answer "c" or…
yeah, bounds written on the type decl shouldn't be repeated on the impl. the current typeck is not smart enough to do that but the ever-"nearly there we promise" replacement is. it'll land one day. they promise
I am the author of a library that requires knowledge and awareness of integers that are strictly not wider than the general purpose register on the processor; the fact that `usize` is "the largest GPR" on every target…
the good news is that a vector of any object can be reduced to a vector of integers by `Box`ing, and then you only incur a miss when you access the data, but not during every step you take to find the data
this magical thinking about standards documents is one of the primary incentives to not have one
yeah this is a common pattern in runtime permissions modelling. it's a really cool trick and i hope it gets more awareness from cases like this
the unstated part here is that in the absence of a compiler-visible atomic modelling system, an atomic model is implemented in `core::atomic` and LLVM. similarly, a `kcore` library could provide atomic types just like…
lol
the main problem here is that C has the capability to declare mmap regions correctly: `volatile char[]` and Rust does not (`[Cell<u8>]` is close but not exactly right, and annoying) most rust folks who use mmap don't…
for one thing, naming a C struct requires more words than naming a Rust struct; for another, the names of functions that operate on them
helps that a 10kloc c program getting riir'd probably won't be a 10kloc rust program, because c doesn't have libraries and rust does. it is literally impossible to write "a small codebase focused on its key value-adds…
No; you should learn Verilog to build a computer. It's a common aspect of Computer Engineering curricula, very educational, and ultimately … not all that useful for most software work, even when doing direct hardware…
Correct. One signature, one body. You can destructure args, but Erlang-style matching or overloading is not a thing. Which sometimes I miss
"I don't need a safety toggle on my gun I just totes keep it pointed at the ground and unloa-- oh god where's my foot"
why isn't it inconsistent to allow creation of a record with missing components but to deny creation of a stack frame with missing components
good
yeah the actual titleholder to those is seattle
rustup is available in your package manager's repository
?
> Rust must stabilize its ABI if it seeks to be a useful systems language. ? no it mustn't. what's the c++ abi
> Having multiple implementations is a sign of a healthy programming language this is frequently taken as axiomatic but there's no actual support for it in reality. there are plenty of healthy single-implementation…
why not
every time this comes up i just have to ask - what do you think a language standard is or does - what languages with standards do you think standardization has helped (this is a trick question! do not answer "c" or…
yeah, bounds written on the type decl shouldn't be repeated on the impl. the current typeck is not smart enough to do that but the ever-"nearly there we promise" replacement is. it'll land one day. they promise
I am the author of a library that requires knowledge and awareness of integers that are strictly not wider than the general purpose register on the processor; the fact that `usize` is "the largest GPR" on every target…
the good news is that a vector of any object can be reduced to a vector of integers by `Box`ing, and then you only incur a miss when you access the data, but not during every step you take to find the data
this magical thinking about standards documents is one of the primary incentives to not have one
yeah this is a common pattern in runtime permissions modelling. it's a really cool trick and i hope it gets more awareness from cases like this
the unstated part here is that in the absence of a compiler-visible atomic modelling system, an atomic model is implemented in `core::atomic` and LLVM. similarly, a `kcore` library could provide atomic types just like…
lol
the main problem here is that C has the capability to declare mmap regions correctly: `volatile char[]` and Rust does not (`[Cell<u8>]` is close but not exactly right, and annoying) most rust folks who use mmap don't…
for one thing, naming a C struct requires more words than naming a Rust struct; for another, the names of functions that operate on them
helps that a 10kloc c program getting riir'd probably won't be a 10kloc rust program, because c doesn't have libraries and rust does. it is literally impossible to write "a small codebase focused on its key value-adds…
No; you should learn Verilog to build a computer. It's a common aspect of Computer Engineering curricula, very educational, and ultimately … not all that useful for most software work, even when doing direct hardware…
Correct. One signature, one body. You can destructure args, but Erlang-style matching or overloading is not a thing. Which sometimes I miss
"I don't need a safety toggle on my gun I just totes keep it pointed at the ground and unloa-- oh god where's my foot"