id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	lang	patch	platform
1662	Should NameSpace entries be available through a hash-like interface?	whiteknight		"Several notes I've run across make references to the fact that NameSpace PMCs should be searchable using a hash-like interface to find entries in the namespace. There aren't a lot of details in these spattered notes, so I don't know whether it suggests we should be able to lookup nested namespaces using such an interface, or NameSpace global entries, or both.

Here's an example of a note from src/global.c:

{{{
NOTE: At present the use of the {get, set}_global functions is mandatory due
      to the wacky namespace typing of the default Parrot namespace.
      Eventually it will be safe to just use the standard hash interface
      (if desired).
}}}

Let's figure out exactly what these notes mean, what we want the NameSpace interface to be, and make everything right."	RFC	new	normal		core	2.4.0	medium