Issue 46: replace WrapperType enum with Strings to allow users to define their own FuncitoDelegates
Project Member Reported by kandpwel...@gmail.com, Jan 31, 2012
Right now, WrapperType does nothing but provide a string representation of the wrapper type to output diagnostic messages in case an exception (i.e., mis-usage) is encountered.  This could be replaced by Strings instead.   There is no other functional use (does not drive logic/decisions).

Normally, I would suggest leaving it closed with the enum, but as OSS, I want to be open to the possibility that others may want to locally add support for other functional-objects (probably other libraries) that don't make it into this product.

The only downside I see is that this would leave open the possibility that others would use Strings which could conflict with Strings that we use in the future if we make additions to supported libraries/wrappable-types.  However, the end result of this is merely that diagnostic messages could become unambiguous for that user only -- until she decides to change her String representation of her new wrapper type.