Jira (PUP-6047) Consider allowing alternative `$name Type` instead of `Type $name` in parameter definitions

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg created an issue   Puppet / PUP-6047 Consider allowing alternative `$name Type` instead of `Type $name` in parameter definitions Issue Type: New Feature Assignee: Unassigned Created: 2016/03/12 7:54 AM Priority: Normal Reporter: Henrik Lindberg In practice it has been found that stating the type before parameters makes it harder to read the code - the reader is typically more interested in the name of the parameter than the type (which is secondary after having found the type). This problem is made worse when complex types are used as the variable name is found somewhere quite far from the beginning of the _expression_. This proposes that the following should be equivalent: function example(Integer $x, String $y = 'hello') { } function example($x Integer, $y String = 'hello') { } If accepted, this should apply to functions, lambdas, defines and classes. 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.