Viewing profile — eddyb

> So what was the screenshot feature of X11? In case I wasn't clear enough, there was never a screenshot feature . Any X11 client could read any pixel written by any other X11 clie…

If you're not familiar, the way X11 works is comparable to "multiplayer notepad" for your pixels ("multiplayer MSPaint"?). All your monitors are combined into a large canvas where …

If your Linux distribution is handling Mesa packages correctly, you will never lack OpenGL/Vulkan drivers . The reason is that Mesa includes "software rendering" drivers for both O…

Not sure if there's a better section elsewhere, but at least this one touches on it: https://doc.rust-lang.org/reference/destructors.html#tempora...

This is effectively a rustdoc bug, the pattern is very much part of the body of the function, not the signature (and this split is explicitly represented in the compiler IRs, which…

> So what are you using or recommending? I am using KDE (aka Plasma5) in Wayland mode, on NixOS unstable. I would not recommend NixOS, just like I mentioned, and I didn't really wa…

GNOME has kind of always been on the opposite end of the configurability spectrum from KDE, IME. But also I'm not super clear on how libinput fits into the picture, I think there u…

> Maybe it would be called #[expect(deprecated)] Both this and the reply saying you should open an RFC worry me that it was tongue-in-cheek. Or maybe it's the obvious name choice, …

We explicitly support building against librustc_driver-*.so for both "custom drivers" (what we call those binaries I mentioned) and generally "rustc as a library" usecases. We shou…

> but also parts of rustc are implemented in a dynamic library ("librustc_driver") Nit: 100% of rustc is found within librustc_driver-*.so (I mention it in https://news.ycombinator…

[continued from above due to size limit] What I'm referring to is incremental recompilation with the following properties: 1. automatic correctness ` - that is, a compiler change n…

No, at most we would've invested more in e.g. ensuring¹ you cannot accidentally (or intentionally) mix-and-match shared objects not built by the same build process, or in ways to r…

It's a shame LLVM isn't more explicit about calling conventions (especially since the front-end has to lower most of the platform-specific C ABI details, short of the exact list of…

Don't you want "interrupt ABIs" for that specific usecase? IIRC `#[naked]` are only really guaranteed to allow inline assembly, so it's like defining a function in `global_asm!` ex…

> For instance `(*role).name` creates a `&mut &'static str` behind the scenes which is illegal, even if we can't observe it because the memory where it points to is not initialized…

I live in Bucharest, Romania and I pay $9/mo for 1Gbps FTTH (fiber into my flat, with an ISP-provided fiber terminal). This offering is available from digi.ro pretty much throughou…

I agree that ARM isn't going anywhere, as long as it can be licensed for less than it takes to design a good-enough RISC-V core, it will get used (with opensource designs slowly lo…

> Or I'm missing something big. It's the software tooling cost. There's nothing exceptional in the spec because it's trying to insert itself into the industry as a standard baselin…

You could look at Cranelift, which I believe uses integer indices, and several datastructures for control-flow vs dataflow. There is no SSA IR in rustc itself (MIR, regrettably, on…

Not at all, RISC-V doesn't need extremely clever compilers, and instead it's designed to maximize what the microarchitectures (hardware implementations) can do, and reduce unnecess…

Betting on smart compilers without putting in the effort to build them is how the Itanic happened.

When I first heard the news, I started imagining EPYC with some core dies replaced with FPGAs connected to the Infinity Fabric. Really cool to hear this used to be a thing with HT …

> but I have not seen any evidence that the average program is actually more likely to behave correctly in the face of wrapping. Rust takes a simple stance of "safe code should be …

I kept grumbling about the `Copy` limitations on iterators for years, but at the end of the day, someone has to write the lint for "iterating on a copy of a variable" and I don't t…

> heterogenous arenas are more or less a solved problem in Rust To expand a bit on what pcwalton said: Rust never had a concept of a type you can't move (we likely can't ever intro…