epeli/underscore.string — pull request #61 by edtsech (2011-11-05 18:17:41+00:00)
Title: Namespace for Underscore.string & 2.0 release

I have created scope for Underscore.string as solution for fixing problems with conflicts with Underscore.
As result Underscore.string will be available in `_.string` and aliased to `_.str` namespace object and will provide function for export all non-conflict methods to Underscore namespace:

_.mixin(_.string.exports())

Conflicts methods will be available through string namespace: `_.str.include`, `_.string.reverse`.

For standalone usage Underscore.string also will be provided as `_.string` if you want you can just override `_`

_ = _.string

And also you can create conflict methods' aliases to `_` namespace for chaining and for work with wrapper-object:

_.includeString = _.str.include
_.reverseString = _.str.reverse

// Now available
_('foobar').includeString('bar')
_('foobar').chain().reverseString().includeString('rab').value()

I think new way will be released as 2.0 version. And will be better switch to [SemVer](http://semver.org/) for versioning.