top | item 13106574

(no title)

Lewisham | 9 years ago

This. It's actually more idiomatic to use the same name, then you can often just sub out one library for another without any hassle.

discuss

order

nkozyra|9 years ago

Unless they have the same functions, variables, structs, etc., sharing the same name really doesn't provide much in terms of hassle-free substitution.

1_2__3|9 years ago

What? No! There's no indication at all these two libraries are compatible - why would you want two completely disparate projects to give some indication they support the same interface?

Lewisham|9 years ago

Because many of the base infrastructure libraries are compatible as long as they used interfaces (grumble grumble os.File). I would be very surprised if this doesn't implement net/http/ServeHTTP

jerf|9 years ago

Then refer to the library by a name, and tell people to import $NAME/mux. You can also name the imports if people want.