Quoting robert engels (2018-12-02 00:59:31)
> Granted, their package structure seems poor in my opinion, but you
> can't talk bad about k8s.
Of course you don't lose anything by getting rid of the package names if
the package structure doesn't make any sense in the first place.
> And probably the most common method signature of them all:
>
> http.HandleFunc("/bar", func(w http.ResponseWriter, r *http.Request) {
>
> are you losing anything if this is:
> http.HandleFunc("/bar", func(w ResponseWriter, r *Request) {
No, and I would go further (if Go permitted it):
http.HandleFunc("/bar", func(w, r) {
...
})
http.HandleFunc is so well known that having the types there at all is
just noise. But I know you don't like type inference.
> All coding requires good development choices - there are many times it
> probably shouldn't be used - but I making a blanket statement its bad
> seems like overreach.
It's bad enough that common Python linters will flag it, and a lot of
large python projects do ban it outright.
Note that nobody in Python land complains about:
from foo import bar, baz
..the equivalent of which is what I've seen in what Java code I have
looked at. Rather, the suspect construct is:
from foo import *
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
