Re: std.path.setExt

2015-06-24 Thread Wyatt via Digitalmars-d
On Wednesday, 24 June 2015 at 20:19:49 UTC, Marc Schütz wrote: On Wednesday, 24 June 2015 at 14:01:32 UTC, Wyatt wrote: I don't think I'd interpret these two names as having the same functionality in the first place. I'd probably learn their equivalence completely by accident and only remember

Re: std.path.setExt

2015-06-24 Thread via Digitalmars-d
On Wednesday, 24 June 2015 at 14:01:32 UTC, Wyatt wrote: On Tuesday, 23 June 2015 at 22:51:08 UTC, Vladimir Panteleev wrote: On Tuesday, 23 June 2015 at 22:45:10 UTC, Vladimir Panteleev wrote: Proposed new name: withExtension I feel this fails the litmus you established before: "These funct

Re: std.path.setExt

2015-06-24 Thread Wyatt via Digitalmars-d
On Tuesday, 23 June 2015 at 22:51:08 UTC, Vladimir Panteleev wrote: On Tuesday, 23 June 2015 at 22:45:10 UTC, Vladimir Panteleev wrote: Proposed new name: withExtension I feel this fails the litmus you established before: "These functions have the same functionality, but one of them is eager

Re: std.path.setExt

2015-06-24 Thread Yazan D via Digitalmars-d
On Tue, 23 Jun 2015 22:51:06 +, Vladimir Panteleev wrote: > Proposed new name: withExtension +1

Re: std.path.setExt

2015-06-23 Thread Jonathan M Davis via Digitalmars-d
On Tuesday, 23 June 2015 at 22:51:08 UTC, Vladimir Panteleev wrote: Proposed new name: withExtension I'm fine with withExtension. Certainly, I don't think that anything starting with "set" really makes sense given that it's a lazy operation. - Jonathan M Davis

Re: std.path.setExt

2015-06-23 Thread Kapps via Digitalmars-d
On Tuesday, 23 June 2015 at 23:13:11 UTC, Mike wrote: `setExtensionLazy` Mike I really don't like the Lazy suffix. Ignoring the issue of making things somewhat uglier solely for the purpose of ambiguity, it also leads to confusion regarding whether you should be invoking foo or fooLazy. Is

Re: std.path.setExt

2015-06-23 Thread Mike via Digitalmars-d
`setExtensionLazy` Rationale * sorts well with `setExtension` for tooling * implies that it is related to `setExtension` in some way * at-a-glance disambiguates it from `setExtension` with a clue as to how it is differrent The disadvantage is that its a little long, but that's due to the leng

std.path.setExt

2015-06-23 Thread Vladimir Panteleev via Digitalmars-d
post. I'll start. Rationale: std.path.setExt is the lazy (range-based) version of std.path.setExtension, thus the only difference in the name is that one is abbreviated, and the other is not. As there is no consistent convention that abbreviated names are lazy, it is not memorable whic