bluss

It all came together very nicely. How to add Copy-specific features is going to be figured out when that bridge needs to be crossed. I think the PR is really...

Have to think more about the module structure. Maybe ArrayVecCopy should just live inside arrayvec::copy. It would be somewhat consistent when the iterator structs need to have that namespace anyway.

Maybe the editing here is missing "the outside perspective from cargo doc" part of the review. Generate doc, look at it, we see stuff we need to add -> module...

I would prefer (1) or (2). I think (1) is on balance the better choice? I don't mind the duplicate `Copy` at all, I think it should be there.

That looks very good but right now, with the slow speed of development, I don't want to use any unstable features.

There are new methods for adding nodes now, so it's possible to fix this up, at least (Not yet released).

Still haven't addressed this issue directly. An API like `Csr::with_nodes(n).with_sorted_edges(xyz)` would be pretty good. Not sure if we can put that into Csr or need a separate builder struct (I'm...

Another curiosity being added to the log here. The following is valid in typst and has effect (the document title is set). Typst version 0.13.1 ```typ #context { set document(title:...

It's the same as good old https://github.com/astral-sh/rye/issues/646

Here's an example of what the shebang rewriting looks like in practice. This kind of technique is called a polyglot script, because it's simultaneously a /bin/sh script and a valid...