>
> But you're not going to get any new syntax accepted by the go team anyway,
> certainly not a new operator. You know that already.
>
I don't know that at all. I'm just putting an idea out there. They may well
consider it or it may inspire other ideas on their part, who knows?
--
You recei
But you're not going to get any new syntax accepted by the go team anyway,
certainly not a new operator. You know that already.
Le vendredi 6 janvier 2017 11:04:38 UTC+1, xjru a écrit :
>
> As I said, this syntax doesn't help, because it puts file into the scope
> of the if block where we often
As I said, this syntax doesn't help, because it puts file into the scope of
the if block where we often don't want it. Reformatting it doesn't change
that.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop
As I said, this syntax puts file into the scope of the if block where.
Reformatting it doesn't change that.
--
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 gola
It would be simpler if Go fmt would let people write if statements on a
single line :
if file,err := os.Open(fname) ; err!=nil { return err }
Here, no need for new syntax and still readable while reducing the
conditional noise. And everybody could be happy.
Le vendredi 6 janvier 2017 01:35:1
