3 ms·
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 su
by 1_2__3 10y 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 10y agoBecause 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
- TheDong 10y agoIt doesn't matter what it's named though, you can always alias the import. If it was "github.com/foo/poppycock" I could just write import mux "github.com/foo/poppycock" and use it as mux. Import name similarity is a terrible argument for picking a name.
- insertnickname 10y agoThere are cases where it makes sense, like https://github.com/pkg/errors https://github.com/pkg/errors which is meant to be a drop-in replacement for the stdlib `errors` package containing a superset of its functionality.