Jira (PUP-3358) conflict between reserved word "type" vs stdlib "type" function

[Hal Deadman (JIRA)]

Title: Message Title

Hal Deadman commented on an issue   Re: conflict between reserved word "type" vs stdlib "type" function Is there a ticket open for the puppetlabs/stdlib having a function that won't work with the future parser? It would be nice if a renamed version of that function could be added to stdlib so modules could easily adopt it. This particular module that is using type() could probably switch to "is_string()" but the type function documentation needs to be updated to discourage further usage. Add Comment   Puppet / PUP-3358 conflict between reserved word "type" vs stdlib "type" function I am using the future parser and the ghoneycutt/hosts module and I am getting errors b/c that module is using the stdlib "type()" function but it is error'ing out because type is now a reserved word. This module stopped working for me after upgrading from 3.6 to 3.7 (using future parser). https://github.com/ghoneycutt/puppet-module-hosts/issues/20 ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.