Jerry D'Antonio

@joelmccracken Perhaps `ImmutableStruct` from concurrent-ruby and its [`#merge` method](http://ruby-concurrency.github.io/concurrent-ruby/Concurrent/ImmutableStruct.html#merge-instance_method) may suit your needs?

@rranelli Certainly, currying would be a great addition. Thank you! Have you already written the blog post? I'd love to read it.

I wasn't aware that Ruby supported currying. Nice find!

@cvb I see that you created a v1.3.0 tag, but the version file still says 1.2.0 and that's the last version uploaded to Rubygems. Had you intended to release 1.3.0?

@cvb I can push to Rubygems when the release is ready. If you don't mind, please remove the 1.3.0 tag and create tag master again once you've updated the version...

I've published it to Rubygems. Thank you!

@andrew-aladev Thank you for your thoughtful feedback. I've made my opinion clear and my opinion has not changed. However, the decision is no longer mine to make. @pitr-ch is now...

That's a very interesting idea. Thank you for suggesting it. Because we are so close to the 1.0 release I've put a feature freeze in place, so we won't be...

I quickly attempted this in PR #465 and many tests failed. It's not something I'm going to attempt right now, with the 1.0 release being so close. We'll make this...

I was under the impression, from a prior discussion with @headius, that autoload was thread safe on both MRI and JRuby. Both the `atomic` and `thread_safe` gems used autoload extensively,...