-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12.05.2014 09:33, anatoly techtonik wrote: > On Mon, May 12, 2014 at 6:00 AM, RjOllos <[email protected]> wrote: >> I've been wondering if we had a consensus, or could reach one on the >> following very minor coding style issue. When a tuple is returned in a >> "return" or "yield" statement, the parenthesis are optional. In the Trac >> codebase there isn't a consistent pattern of choosing one pattern. I tend to >> prefer the minimal approach of omitting the parenthesis. >> >> I was hoping to add a rule to >> http://trac.edgewall.org/wiki/TracDev/CodingStyle. > > How about readability for people from other languages? They will need > to Google for comma, which is hard.
Yes, personally I lean towards explicit rather than implicit too. I remember having a hard time to understand this implicit return object type definition on my own. Not seen a decent documentation on in yet, but I did not look too much for it either. Maybe due to not knowing a good keyword, what would be further indication, that Anatoly is right with that assertion. Steffen Hoffmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNz2IUACgkQ31DJeiZFuHcU6ACg2Z8DnjChRRR1vJKBuzSh6Z/i mC4AoJ8tMrQOn09985S7K9g4TUIeupHT =BCKc -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
