feat!: Use a radix trie for route matching

[ElijahAhianyo]

Description

The current router implementation uses a Vec to store routers, which has some real limitations. For example, using a vec meant route conflict detection was cumbersome and hacky to get right. Using a Radix trie is the right data structure for this problem. This PR delegates the core Trie logic to the matchit crate. We still keep our business logic in a light wrapper over the Matchit Router.

Breaking Changes

1. Registering a route with a duplicate parameter at the same segment will now fail

Router::with_urls([
    Route::with_handler_and_name("/foo/{bar}", index, "index"),
        Route::with_handler_and_name("/foo/{baz}", add_example_form, "add"),
])

2. Registering 2 views with the same url_prefix will fail

struct TestProject;
impl Project for TestProject {
   ...
    fn register_apps(&self, apps: &mut AppBuilder, _context: &RegisterAppsContext) {
        apps.register_with_views(App1, "");
        apps.register_with_views(App2, "");
    }
}

3. When a handler and router are registered for the same route, the handler will take precedence at lookup time

let nested_router = Router::with_urls([Route::with_handler_and_name(
        "/inner/{id}",
        nested,
       "nested",
)]);

Router::with_urls([
    Route::with_handler_and_name("/foo", index, "index"),
    Route::with_router("/foo", nested_router),
])

4. A route is treated as different from its trailing-slash counterpart:

Router::with_urls([
    Route::with_handler_and_name("/foo", index, "index"),
    Route::with_handler_and_name("/foo/", another_handler, "another" ),
])

5. This does not apply to routers. The example below is invalid and will fail:

Router::with_urls([
    Route::with_router("/foo", nested_router_a),
    Route::with_router("/foo/", nested_router_b ),
])

Type of change

• Bug fix
• New feature
• Documentation
• Refactor / cleanup
• Performance improvement
• Other (describe above)

[github-actions]

Bencher Report

Project	cot
Branch	elijah/router-trie
Testbed	github-ubuntu-latest

Click to view all benchmark results

Benchmark	Latency	Benchmark Result milliseconds (ms) (Result Δ%)	Upper Boundary milliseconds (ms) (Limit %)
empty_router/empty_router	📈 view plot 🚷 view threshold	14.97 ms (+60.08%) Baseline: 9.35 ms	17.77 ms (84.22%)
json_api/json_api	📈 view plot 🚷 view threshold	1.14 ms (+10.88%) Baseline: 1.03 ms	1.37 ms (83.69%)
nested_routers/nested_routers	📈 view plot 🚷 view threshold	1.10 ms (+14.24%) Baseline: 0.97 ms	1.26 ms (87.70%)
single_root_route/single_root_route	📈 view plot 🚷 view threshold	1.03 ms (+11.18%) Baseline: 0.93 ms	1.22 ms (84.68%)
single_root_route_burst/single_root_route_burst	📈 view plot 🚷 view threshold	19.51 ms (+15.89%) Baseline: 16.84 ms	21.47 ms (90.89%)

🐰 View full continuous benchmarking report in Bencher

[ElijahAhianyo]

Should be rebased on and merged after #586

[m4tx]

Do we have any way of registering multiple routers at the same URL? This is an important feature - people might want to merge different routers at the same base URL.

If matchit doesn't let us do that because it detects a conflict, we should merge the routers. I'm not sure if we should have separate methods to do that explicitly, or keep the implicit behavior - I'll let you decide.

[m4tx]

Why not just use expect here?