router match mistake, when define named pattern and simple pattern simultaneously about trie-mux HOT 5 CLOSED

There is Otherwise mathod on your demand

from trie-mux.

It can't support implicit matching.

You should define router.Get("/a", handler)

from trie-mux.

In my opinion, simple pattern take precedence over named pattern, /a conflict with /:a, if both of them exist, maybe there should be a panic.

There is other situation

package main

import (
    "net/http"
    "github.com/teambition/trie-mux/mux"
)

func main() {
    router := mux.New()
    router.Get("/a/b", func(w http.ResponseWriter, _ *http.Request, _ mux.Params) {
        w.Write([]byte("hello world!\n"))
    })

    router.Get("/:name/b", func(w http.ResponseWriter, _ *http.Request, _ mux.Params) {
        w.Write([]byte("index\n"))
    })

    http.ListenAndServe(":8080", router)
}

/a/b is conflict with /:name/b, path /b/b match /:name/b, but it's difficult to find the conflict between them, i can't solve this, so i post a issue.

from trie-mux.

Currently it is enough for practice usage with high performance. Don't make logic intricacy.

from trie-mux.

Yes, beyond is as wrong as falling short.

from trie-mux.