Now that we're 1.20+ instead of 1.14+ we can use 1.18's strings.Cut in a
few places to simplify code.

This is a new go vet analysis pass that fires under go 1.24:

  $ go1.24rc2 vet ./...
  # github.com/go-chi/chi/v5
  # [github.com/go-chi/chi/v5]
  ./mux_test.go:236:12: non-constant format string in call to (*testing.common).Fatalf
  ...

The strings would be parsed as format strings which is not intended.
See golang/go#60529 for details.

This also bumps the minimum supported version of Go to 1.16 (which itself has beel EOL for almost 3 years now)

Co-authored-by: Vojtech Vitek (golang.cz) <[email protected]>

GHSA-vrw8-fxc6-2r93

Advisory reported by Anuraag Baishya, @anuraagbaishya. Thank you!

It appears as though regular expression quantity support was added by
#245. This updates the documentation to reflect that.

Allow separating the method and pattern with [ \t]+, this matches the
stdlib change that was made in golang/go@7b583fd

The rationale is the same as the stdlib issue, it allows you to visually
line up patterns with variable-width methods:

  r.Handle("GET    /my-route", handler1)
  r.Handle("POST   /my-route", handler2)
  r.Handle("DELETE /my-route", handler3)

In general aligning ourselves with the stdlib brings less surprise for
end users.

Fixes: 0fe6bf1 ("Use RoutePath in URLFormat middleware (#718)")
Found by PostgresPro with Svace Static Analyzer

Signed-off-by: Maksim Korotkov <[email protected]>

Similar to #901

Adds support to get the pattern that was used by Chi to match the route,
without needing to call the Chi context.

…sage (#1016)

* chore: remove comment from TestThrottleRetryAfter test

* test: fix flaky TestThrottleRetryAfter by synchronizing token usage

…1011)

- Only create time.NewTimer() when actually needed to wait
- Reduces allocations from 7 to 4 and memory usage by ~54%
- Improves performance by ~50% in high-throughput scenarios

…wildcards (#1012)

Co-authored-by: srpvpn <[email protected]>

This code predates the introduction of the reverseMethodMap.