Naming schemes
John Colvin via Digitalmars-d
digitalmars-d at puremagic.com
Wed Jun 24 06:45:26 PDT 2015
On Wednesday, 24 June 2015 at 13:40:28 UTC, Vladimir Panteleev
wrote:
> On Wednesday, 24 June 2015 at 13:27:17 UTC, Vladimir Panteleev
> wrote:
>> On Tuesday, 23 June 2015 at 23:58:07 UTC, Jeremy Powers wrote:
>>> I actually don't think having separate threads for each name
>>> is the best solution. May be better to get them all listed
>>> in one place, and see if a consistent naming system can
>>> emerge.
>>
>> I looked through std.range and std.algorithm and created this
>> page:
>>
>> http://wiki.dlang.org/Naming_conventions
>
> BTW, as for eager/mutating functions, they are almost all verbs:
>
> == std.algorithm ==
> sort
> schwartzSort
> largestPartialIntersection
> bringToFront
> copy
> fill
> moveAll
> moveSome
> remove
>
> == std.array ==
> join
> replace
> split
> replicate
Which is sensible. A range is an object that performs an action,
an eager function is the action itself.
More information about the Digitalmars-d
mailing list