Jira (PUP-1029) filter function should accept two parameters

Henrik Lindberg (JIRA) Fri, 07 Feb 2014 14:48:15 -0800

Title: Message Title

Henrik Lindberg commented on an issue

For Functional Review:

The functions each, map, and filter should be consistent w.r.t how index/value, and key/value is used:
One parameter gets the value
Two parameters is index/value for all enumerables except hash which gets key/value
The reduce function always receives two parameters; memo and value (index/key feature is not available).
The slice function is different (it hacks of a chunk and feeds it to the block) and index/key is not relevant in this case.
All iterative functions should be able to operate on:
Array
Hash
Integer range (e.g. Integer[2,7])
an integer (defines 0-n times)
String (as if it were an Array of single character entries)
All iterative functions should give informative errors when:
the LHS is not enumerable (say a Float, or a Regexp)
there are to many/few parameters specified in the block

Test with code like:

                                                    puppet apply --parser future -e 'notice "abc".reduce |$memo, $c| { "$c$memo" }'

                                                

Read through documentation of the iterative functions.

Add Comment

Puppet /

PUP-1029

The filter function should accept two keys for all LHS types; key/value, or index/value to make it consistent with each and map.

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1029) filter function should accept two parameters

Reply via email to