Support immutable contexts about web HOT 2 CLOSED

At a bare minimum, I think this would double the number the number of signatures that gocraft/web has to deal with for middleware. Also, how do you propose handling the fact that the context type of the middleware in a subrouter can be an extension(via embedding) of the context above it? This may not be as problematic as I suspect.

Also, why do you think contexts are automatically thread-safe? Copying an object in Go does not automatically create something thread-safe. For example, go create a copy of a big.Int. You'll find that changes to the copy can affect the original.

from web.

@ohler I don't think I'm interested in supporting immutable contexts or go.net/context. They're both fine ideas, but incompatible with the design of gocraft/web.

from web.