You're right Chesnay, I didn't remember that .of was introduced :(
Sorry!
On Fri, Mar 22, 2019 at 12:35 PM Chesnay Schepler
wrote:
> You could even use a method reference here: "map(Row::of)"
>
> On 22/03/2019 12:33, Chesnay Schepler wrote:
> > I can see that this would be convenient but please
You could even use a method reference here: "map(Row::of)"
On 22/03/2019 12:33, Chesnay Schepler wrote:
I can see that this would be convenient but please find a better
example; yours can be solved easily using "Row.of(value)".
On 22/03/2019 12:26, Flavio Pompermaier wrote:
Hi all,
many times
I can see that this would be convenient but please find a better
example; yours can be solved easily using "Row.of(value)".
On 22/03/2019 12:26, Flavio Pompermaier wrote:
Hi all,
many times I had the feeling that allowing Row.setField() to return the
modified object instead of void would really
Hi all,
many times I had the feeling that allowing Row.setField() to return the
modified object instead of void would really make the (Java) code cleaner
in a very unobtrusive way.
For example, I could write something like:
DataSet columnData = input.map(value -> new Row(1).setField(0, value))
in
