Jira (PUP-5898) Data types seems to be messed up on hash parameters

[Reinhard Vicinus (JIRA)]

Title: Message Title

Reinhard Vicinus created an issue   Puppet / PUP-5898 Data types seems to be messed up on hash parameters Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Unassigned Components: Language Created: 2016/02/13 3:48 AM Priority: Normal Reporter: Reinhard Vicinus The following code: define test ($b) { $a = { key => undef } notice("a: $a") notice("b: $b") $a.each |Array $values| { notice("a values: $values") } $b.each |Array $values| { notice("b values: $values") } }   $a = { key => undef } test { "test": b => $a, } generates the following output if run with puppet apply: puppet apply test.pp Notice: Scope(Test[test]): a: {key => } Notice: Scope(Test[test]): b: {key => } Notice: Scope(Test[test]): a values: [key, ] Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Method call, block parameter 'values' expects an Array value, got Tuple at /home/rvicinus/test.pp:8:5 at /home/rvicinus/test.pp:14 on node puppetmaster I would expect that the second each statement would run like the first, because the supplied hash is absolutely equally created like the one provided to the first each statement. I think somehow assigning the hash to a parameter messes up the data types, because the code works as expected if the Array keyword in the second each statement is removed. This is also the workaround that I use. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.