The common term for this kind of thing is “full-bleed”. It's a term borrowed from the publishing world; when something is printed full-bleed, it extends to the very edge of the paper.
This new requirement makes the problem considerably more tricky. It's relatively easy to constrain all children, but CSS doesn't really have a mechanism to selectively constrain some children.
Source: CSS Grid full-bleed layout tutorial, an article by Josh W Comeau.
I show how two domain-specific type systems, information flow control and two-party communication protocols, can be implemented in Rust using type-level programming. I explain how interesting properties of these domains can be verified at compile-time. Finally, I construct a general correspondence between type operators, logic programs, and their encoding in Rust.
Source: Type-level Programming in Rust, an article by Will Crichton.
Okay, I admit it: I could have given this article all sorts of alternative titles, each of which would have made as much sense as the one I chose. I didn't want to go with some of the other titles I had in mind, because they would give it all away up front. I didn't want to spoil the surprise.
I recently ran into this bug, it took me hours to troubleshoot it, and I was appalled when I realised what the problem was.
This is the story of that bug.
There are several insights from this story, and I admit that I picked the most click-baity one for the title.
Source: Fortunately, I don't squash my commits, an article by Mark Seemann.