Viewing profile — myrrlyn

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

> C is an amazing language [citation needed] > the best way to use C is to use it to implement core algorithms and data structures is this a joke. you literally cannot write contai…

lol.

given that the sole purpose of software is to do what people want, "it didn't do what i want" is automatically incorrect behavior

is this going well for you

?

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

why not

(there are none)

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

PRs welcome!

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…

the reason for > I still feel uneasy depending on so many other crates, but this seems to be a level of paranoia that others in the community don't share. Having 1000 dependencies …

> What slice of Rust users are both such noobs they haven’t heard of cargo-edit and can’t Google it, but also so advanced they are interested in implementing Future manually to dee…

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

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 …

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…

unless you plan to run `rustc` as a kernelspace application, anything in tier 2 (`core`, `alloc`, maybe `std` all compile and likely pass tests) is sufficient

putting my marker on 2030 as implementing a tokio runtime in kernelspace