Why is array.reverse a property and not a method?
bearophile
bearophileHUGS at lycos.com
Mon Jul 12 12:57:36 PDT 2010
Andrei Alexandrescu:
> std.conv -> std.conversion
OK.
> std.stdio -> std.io
OK.
> put(R, E) -> putNext(R, E)
Uhm. I don't like this a lot.
> BidirectionalRange -> DoublyEndedRange
Acceptable.
More suggestions:
std.cover => std.coverage
Rationale: this module is not used very often, so by Zipf law you can use the full word.
std.typecons => std.records (that contains Record/record)
std.typetuple => std.tuples (that contains Tuple)
Rationale: a "typetuple" can contain values too, and structs have a tupleof method, not a typetupleof method.
std.concurrency/std.thread => std.concurrency
std.metastrings/std.traits => std.meta
std.bitmanip => std.bits ?
Rationale: 'bitmanip' is not a nice name.
std.date/std.gregorian => std.time ?
std.range => std.ranges ?
std.regex/std.regexp => std.re (as in Python) ?
Rationale: in certain kinds of modules this is used often, but 'regex' name too is acceptable.
Bye,
bearophile
More information about the Digitalmars-d
mailing list