Jira (PUP-1942) Add 4x global scope

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Add 4x global scope Also see PUP-1943 for API concerns regarding "not found" only strings are acceptable for names names should not start with :: - if they do when writing, they should be stripped an empty string is not acceptable as a name reserved names can only be set via a special privileged set method (in 3.x this is done by passing an option, but it should be a separate method instead for performance reasons). only the privileged set method may set the reserved names changing an already bound name is not allowed (runtime error) it is allowed to bind nil/undef as a value Add Comment   Puppet / PUP-1942 Add 4x global scope As part of the implementation of 4x scope, there should be a global scope that: * maps qualified names to values (or resolver of value) * name to value mapping is per "kind" supported by the runtime (i.e. function, class, user defined type, variable) * allows a name to be bound to "it is know to not exist" The implementation is performance critical.... 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.