Howard M. Lewis Ship

I know I'd love to see this; I'm really curious to see how my app performs with erlang 24 and the JIT.

I've been deploying using Dokku on Digital Ocean, so there's a lot of the stack I don't (yet?) understand.

I've completely rewritten the tutorial as well as other documentation.

This does seem like a bug; at first I was going to point out that wildcards routes always "win" but that's not the case here.

I'm looking this over, but I believe that routing is correct because, yes wildcards win out. I think you might be able to leverage constraints to accomplish both, I'm going...

Here's some findings: ``` (defn- attempt-route ([routes request] (attempt-route routes :prefix-tree request)) ([routes kind request] (let [ctor (get route/router-implementations kind) router (ctor (expand-routes routes)) request' (merge {:request-method :get} request)] (router/find-route...

One could imaging that the prefix would map to a seq of routes, not a single one, ordered by specificity, and attempt to match each of them. That being said,...

Again, I think changing the current prefix tree router now is extremely risky due to the high probability of unforeseen consequences affecting existing applications. Still, Alex's idea is that we...

Looking over the above, I don't see anything actionable beyond, perhaps, ongoing documentation improvements, or a new router. In the meantime, I'm closing this issue.

This seems incomplete; there's no tests, and no API for extracting the named operation from the map. I'm just not sure what's the point of this change.