On 08/15/2012 06:10 PM, Gareth Smith wrote: > I guess this is also an issue when type names are used in non-constructor > functions: e.g. should the to_str method actually be called to_Str, should > to_bytes be called to_Bytes ?
why not camel-case everywhere, starting with a lower-case letter for
functions and with a upper-case letter for types? Then these methods would
become toStr, toBytes, matching the type names.
I always find the convention to use underscores in some names and camel-case
in others a bit unnatural and contrived. Also, on German and other
keyboards, where typing _ requires the caps key, to_str is one keystroke
more than toStr, which is a point of favor of camelCase.
Best regards
Christian
--
|------- Dr. Christian Siefkes ------- [email protected] -------
| Homepage: http://www.siefkes.net/ | Blog: http://www.keimform.de/
| Peer Production Everywhere: http://peerconomy.org/wiki/
|---------------------------------- OpenPGP Key ID: 0x346452D8 --
Productivity ought to mean achieving more in an hour of work, but all to
often it has come to mean extracting more for an hour of pay... managers
dream of attaining new productivity levels through the simple mechanism of
unpaid overtime. They divide whatever work is done in a week by forty
hours, not by the eighty or ninety hours that a worker actually put in.
That's not exactly productivity--it's more like fraud--but it's the state
of the art for many American managers.
-- Tom DeMarco and Timothy Lister, Peopleware
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
