FlatMapper

[Joe Bowbeer]

Last time we were looking for a descriptive name not necessarily a great
name.

flattenInto does a good job of referencing its interface, while mapInto is
more ambiguous in that respect.

Is mapInto more easily confused with other names such as 'collect'?

 Is mapInto better than flattenInto?  Still trivial to change at this point.

On 2/21/2013 11:33 AM, Kevin Bourrillion wrote:

> Tardy, but:  the Googlers I ran this by all felt just fine with
> "mapInto".  Sure, you can map /multiple, /but that fact just didn't seem
> overly necessary to force into the name.
>
> On Sun, Feb 17, 2013 at 12:29 PM, Joe Bowbeer <joe.bowbeer at gmail.com
> <mailto:joe.bowbeer at gmail.com>**> wrote:
>
>     flattenInto gets my vote
>
>     On Feb 17, 2013 11:09 AM, "Remi Forax" <forax at univ-mlv.fr
>     <mailto:forax at univ-mlv.fr>> wrote:
>
>         On 02/17/2013 08:07 PM, Brian Goetz wrote:
>
>             flattenInto seems the best so far.
>
>
>         +1
>
>         Rémi
>
>
>             On 2/17/2013 9:36 AM, Tim Peierls wrote:
>
>                 On Sun, Feb 17, 2013 at 6:17 AM, Remi Forax
>                 <forax at univ-mlv.fr <mailto:forax at univ-mlv.fr>
>                 <mailto:forax at univ-mlv.fr <mailto:forax at univ-mlv.fr>>>
>                 wrote:
>
>                      mapAndFlattenInto is a little to verbose for me,
>                 mapAndFlat ?
>
>
>                 No, has to be a verb.
>
>                 I'd still understand flattenInto, leaving the mapping
>                 part to be implied
>                 by the type name.
>
>                 --tim
>
>
>
>
>
> --
> Kevin Bourrillion | Java Librarian | Google, Inc. |kevinb at google.com
> <mailto:kevinb at google.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/lambda-libs-spec-experts/attachments/20130221/8fd63df7/attachment.html