Carl Mäsak

This issue is a little bit related to #527; in fact, `min` and `max` can probably be implemented in terms of `reduce`.

Note: tc39 currently has a [slice syntax proposal](https://github.com/tc39/proposal-slice-notation) going.

Reading the tc39 proposal, I'm struck by a number of things: * Using Perl 6 `..` and `..^` (and `^..`) syntax might not be such a bad idea after all....

> But... let's not introduce more problems than we need; let's stick with `array[x:y]` (and `array[x:y:z]`) for now. I no longer believe that to be the right trade-off. Instead I...

Another nice force multiplier would be being able to do `array[from..to] .= reverse()`; that is, combining array slicing and the `.=` operator. As far as I can see, that follows...

About some of these, code of conduct, issue templates, pull request templates, I don't feel like imposing any more structure than absolutely necessary for the project. But I'll have a...

I'm tempted to go with [the Fedora Project CoC](https://docs.fedoraproject.org/en-US/project/code-of-conduct/index.html). When I started reading different ones, this turns out to be the one the Django project is ultimately based on. The...

[This README template](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2) is not bad. Maybe we can incorporate some of those points in our README.

How would unquotes interact with visitors? If we were boring, we would perhaps say that visitors never recurse into `Q::Quasi` structures. But we're not boring, we're adventurous. Will we be...

Based on what I've been doing lately with the 007, I think visitors will want a postponing mechanism. Proposal: provide a `do_later` method on the visitor. It takes a callback...