Ibraheem Ahmed

>So for example from these paths: ``` /{}ello-world /hello{}world /hello-{} ``` >/hello-world would be matched by the last, right? Yes, that is correct, though I didn't fully consider the implications...

> This change will lead to a subtle difference between nest and nest-service. > For example the following test behaves differently with the two methods: I don't fully understand why...

> I think this is fine and we can just document the behavior and maybe discourage mixing of prefixes and suffixes in the same node. I can't really think right...

> Or would you allow \pre{x} with \prefix{x}suffix? Hm yeah this also might be problematic. You might be right that a given list of overlapping route segments can include, in...

The new rules have been released as part of matchit 0.9.0. The only change that might be considered breaking from 0.8.4 to 0.9.0 was https://github.com/ibraheemdev/matchit/pull/60, but I would consider that...

Work in progress [on this branch](https://github.com/ibraheemdev/matchit/tree/prefix-suffix-conflict) that implements the new rules: > A given list of overlapping route segments can include, in order of priority, > - Any number of...

Sorry, I don't remember the exact state of the code on that branch. It's possible that it just needs more tests. For some context, there are a couple of different...

The new rules have been implemented and [released in 0.9.0](https://github.com/ibraheemdev/matchit/releases/tag/v0.9.0).

Sorry for the late reply, this issue slipped from my notifications. You can use [`Body::wrap_reader`](https://docs.rs/astra/latest/astra/struct.Body.html#method.wrap_reader) to stream an HTML file response.

Hi, I'm a little crunched for time at the moment. I do plan to upgrade to Hyper 1.0 at some point, unfortunately I can't give you a concrete timeline. Also...