FlatMapper (original) (raw)

Kevin Bourrillion kevinb at google.com
Thu Feb 21 08:43:36 PST 2013

emit()?

On Thu, Feb 21, 2013 at 8:42 AM, Kevin Bourrillion <kevinb at google.com>wrote:

I believe the mapping aspect is an order of magnitude more relevant than the flattening aspect. The way we've designed the API, nothing is exactly being flattened, anyway. It's just that multiple results may be emitted.

On Thu, Feb 21, 2013 at 8:35 AM, Brian Goetz <brian.goetz at oracle.com>wrote: 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> -- Kevin Bourrillion | Java Librarian | Google, Inc. | kevinb at google.com

-- Kevin Bourrillion | Java Librarian | Google, Inc. | kevinb at google.com

More information about the lambda-libs-spec-observers mailing list