RFC: Convert all Puppet 4.x API functions to namespaced variants

[alexjfisher]

IMO, only core puppet functions should not have namespaces, and all stdlib functions should start stdlib::.

I'd like to suggest that all current 'modern' (non 3.x style) functions get converted to namespaced versions with a non-namespaced deprecated shim replacing the original file in the same way as is done here.

This was also the approach we took in [extlib](https://github.com/voxpupuli/puppet-extlib/pull/120) and [postgresql](https://github.com/puppetlabs/puppetlabs-postgresql/commit/700d2c5bb54b7ea91d518de96e2c7a22318d0afa).

In a future major release we could drop the shims similar to how we did in [extlib 5.0.0](https://github.com/voxpupuli/puppet-extlib/pull/153)

[chelnak]

I think this is a reasonable suggestion.

Lets put it out to the wider community too (i'm sure many have already seen).. and get some votes.

[alexjfisher]

If this is the way we want to go, then perhaps either a rake task or some sort of helper (or both!) could reduce the tedious repetitiveness of creating the shims?? @ekohl - Any thoughts?

[ekohl]

I wonder if you need to declare them in the same filename as the function. Perhaps you could generate them in a for loop.

[alexjfisher]

Ooh, maybe that could work. Or maybe you do if you want puppet-strings to mention them??

[alexjfisher]

Actually, I think a function can only be loaded if it's in the correct file.

[alexjfisher]

and it has to have a call to create_function in it.

The code loaded from modules/stdlib/lib/puppet/functions/foo.rb does not seem to be a Puppet 4x API function - no create_function call.