Good name for f.byLine.map!(x => x.idup)?

w0rp devw0rp at gmail.com
Sun Mar 16 15:36:10 PDT 2014


On Sunday, 16 March 2014 at 21:16:24 UTC, bearophile wrote:
> Joseph Rushton Wakeling:
>
>> Sorry, didn't get far enough through the thread to see other 
>> people had already suggested this one.
>
> Suggesting it again is useful, because it means more people 
> find that name sufficiently intuitive. So perhaps "byLineCopy" 
> could be the winner name.
>
> Bye,
> bearophile

byLineCopy seems good to me. It *may* be an idea to change the 
name of byLine very slowly via a long deprecation process so 
newcomers to the language don't start accidentally grabbing the 
shorter more obvious choice and run into problems when they are 
surprised by the semantics. byLineRef or some kind of thing. Just 
ignore me if that's a bad suggestion. I just kind of have this 
symmetry where if I have something named say "doFooSafely" I 
don't call the unsafe one "doFoo," I call it "doFooDangerously" 
or something obvious. Not that byLine is particularly "unsafe."

I considered calling a method named "disableGC" in DQt 
"createMemoryLeaks," but I decided that was pushing it a little 
too far. (It's a weird thing, but you actually need to use it 
some times. At least it's @system.)


More information about the Digitalmars-d mailing list