Results : Standard Lambda Utils Survey #1
Mike Duigou
mike.duigou at oracle.com
Fri Aug 12 09:17:13 PDT 2011
The original version of this message really did have results in it as a lovely colourful graph. The graph was however stripped by the mailing list software. I guess I was being punished for not including accessible alt text.
In raw form here are the results:
11 Yes, copying the source collection "blocks" avoids errors.
9 Yes, copying the source collection "blocks" ensures that the lambda function has consistent results.
66 No, if I am worried about the source collection changing I will copy it myself before passing it to the util methods.
16 No, changing the lambda function behaviour by changing the source collection "blocks" is useful.
50 No, copying the source collection "blocks" costs too much.
13 No, unless the elements of the source collection "blocks" are also cloned then it's not worth bothering.
27 No, even with copying it's still possible that elements of the copied collection "each" might change in some way so even don't try.
30 Other (please specify)
===
104 voters
Thanks again to all who responded and refrained from discussing the survey on the list until these results appeared.
Mike
On Aug 12 2011, at 09:03 , Mike Duigou wrote:
> As was expected the results of the survey question greatly favoured not copying the source collections.
>
> With 104 responses the results were:
>
>
> Multiple choices could be selected. Full text of options was :
>
> Yes, copying the source collection "blocks" avoids errors.
> Yes, copying the source collection "blocks" ensures that the lambda function has consistent results.
> No, if I am worried about the source collection changing I will copy it myself before passing it to the util methods.
> No, changing the lambda function behaviour by changing the source collection "blocks" is useful.
> No, copying the source collection "blocks" costs too much.
> No, unless the elements of the source collection "blocks" are also cloned then it's not worth bothering.
> No, even with copying it's still possible that elements of the copied collection "each" might change in some way so even don't try.
> Other (please specify)
>
> The next committed rev of the lambda utils will eliminate defensive copying of the source lambdas.
>
> Mike
>
More information about the lambda-dev
mailing list