estebank

25 ms·

451.
by estebank 2y ago
> I do hope rustc gets better at lifetime compilation errors cause some of them can be very very gnarly. When this happens, file tickets! We do our best to improve diagnostics over time, but the best improvements have been reactive, by f
452.
by estebank 2y ago
You mean like `clippy::let_underscore_lock`? I'd like it if there was an annotation for arbitrary types to declare that they behave like a lock so that the lint would pick them up too.
453.
by estebank 2y ago
Technically, so did the SNES with the NES, it was just never really exposed. SMB all-stars started as SMB3 running directly on SNES. And you had the Super GameBoy, but that was little more than a GameBoy in a cartridge.
454.
by estebank 2y ago
If you care about this rule, you can deny it on your projects (at the crate level or for individual items), but if it were an unconditional error then it would make things like FFI or following non-Rust naming conventions either annoying or
455.
by estebank 2y ago
The track pad and keyboard don't need to move, which would introduce mechanical stress on the port and cable.
456.
by estebank 2y ago
I get what they were going for: force the user to use it as intended because the battery really lasted long enough for most people. Otherwise people would just have left it plugged always, and the cable+port would have needed different mech
457.
by estebank 2y ago
On the one hand, I think that it would be a winning strategy. On the other, that effectively turns C++ part of the Rust language. And that is even before looking at the need to extend the Rust compiler to express things that the Rust langua
458.
by estebank 2y ago
The thing is, if you were to make the same design in C++ the code might look "cleaner" because there is less code/fewer annotations, but the other side of that coin is that the developer also has less information about how
459.
by estebank 2y ago
Well, I do describe Japan as "Kawaii Germany".
460.
by estebank 2y ago
*73%
461.
by estebank 2y ago
For this kind of analysis, https://github.com/geiger-rs/cargo-geiger comes in handy.
462.
by estebank 2y ago
It wasn't until this comment that made me realize that using "written in Rust" as rage click bait is such a "useful" strategy here, because it will inevitably attract plenty of comments about the mentioning of the
463.
by estebank 2y ago
Why is there a conflation between "modern" and "unstable", and "conventional" and "solid"? I've seen plenty of conventional things that are not solid, and plenty of modern things that were far fr
464.
by estebank 2y ago
I saw some time back that a productionalized attempt came out: https://github.com/magic-wormhole/magic-wormhole.rs The one I mentioned was much more primitive, meant as a demo (you can look at the branches for differen
465.
by estebank 2y ago
When comparing a networked service that wrote to disk (a-la magic wormhole) written in Java and in Rust, after 3 iterations of improvements on the respective implementations the throughput was the same for both, CPU utilization was compar
466.
by estebank 2y ago
> They will be slightly slower due to often using indexes instead of raw pointer, which requires a bound check and an addition to get the pointer, and sometimes a reallocation, but they won't be that slow. This is not a fundamental
467.
by estebank 2y ago
> I have my doubts how long this will scale when Rust has like 40 years of history behind it. We've been doing this for 10 years already, so if the cost is linear, it shouldn't be a problematic burden over another 30 years. It
468.
by estebank 2y ago
> The fact that the certified toolchain is just the normal, publicly available one is great too. And speaks to the standards of quality that the project holds itself to.
469.
by estebank 2y ago
You might also want to check out this comparison of MISRA's rules against idiomatic Rust code: https://github.com/PolySync/misra-rust/blob/master/MISRA-Rul...
470.
by estebank 2y ago
Its not so much about ensuring the best tool chain is used, but rather about setting the lowest bound of quality. By being slow moving it avoids the potential for temporary regressions. It is also ass-covering by demonstrating you followed
471.
by estebank 2y ago
The former. Effects is not something that should have blocked 1.0 at all, that was the right call. Don't think it was even on the table back then.
472.
by estebank 2y ago
> By default Rust's release builds give the integer overflows wrapping, so (1u8 + 255u8 == 0u8) rather than panic, so as to avoid paying for the checks. I consider that to have been a mistake, and hopefully one we can change. Note t
473.
by estebank 2y ago
> the uptick in new citizens is due to efforts to reduce a backlog of applications that began during the Trump administration and exploded amid the COVID-19 pandemic.
474.
by estebank 2y ago
I've noticed that having even a minimal implementation helps a lot to inform the RFC: some details are non-obvious until you are either forced to clamp down behavior or have tried to use the feature. The RFC discussion doesn't alw
475.
by estebank 2y ago
> but is it going to be the same in, say, 15 years? You would think that by then either the Rust experiment has failed or the project has gained enough experienced developers such that maintaining such large refactors is feasible beyond
476.
by estebank 2y ago
> I think in many situations it is just as safe to nearly-but-not-completely come to a full stop before continuing, and it's entirely fine behavior. I'm sure the multiple people that would have hit me if I hadn't jumped ou
477.
by estebank 2y ago
I've seen crates like that: APIs with very complex trait bounds that require one to sit down with a cup of tea to pour over before you can understand what they do. I don't particularly like those. What APIs written that way enable
478.
by estebank 2y ago
The Linux kernel is stable for userspace only. Drivers are expected to be merged up stream and the internal APIs change often with no regard for out of tree drivers. So there's no interface that an alternative kernel can target that do
479.
by estebank 2y ago
If you encounter compiler errors that are misleading in their suggestions, or have proposals for better output in specific cases, please file a ticket: https://github.com/rust-lang/rust/issues?q=is%3Aissue+label%..
480.
by estebank 2y ago
> because he doesn't want kids to be transitioned and doesn't think people that say mean things (or things someone in particular thinks are mean) are automatically bad people. Characterising the critiques of Musk in this way is

More ›