Add reset! command

[atomaka]

Allow users to clear our current object cache. This is particularly useful when Unique is being used in combination with RSpec and Faker.

[b264]

I was thinking about this sort of functionality as well, but this seems like the poster-child use-case for a stateful class. I was thinking something like

unique_set1= Unique.new{ 1 }
unique_set2= Unique.new{ 1 }

unique_set1.take
 => 1
unique_set1.take
Unique::NoUniqueObjects: An unused, unique object could not be found in 4096 tries
unique_set2.take
 => 1
unique_set2.take
Unique::NoUniqueObjects: An unused, unique object could not be found in 4096 tries

Unique.config.max_tries= 10

...and possibly a module-level scope as well (or not .. ?? )
Unique.next!{ 1 }
 => 1
Unique.next!{ 1 }
Unique::NoUniqueObjects: An unused, unique object could not be found in 4096 tries

I think this could do everything as a reset command, plus more, in a more intuitive manner. Any thoughts about this? The downsides of the module-level approach is that it could use a lot of memory if left running for a long time, whereas the class approach would work very well for testing and shouldn't leak memory. If it's used outside of testing, anyway. The purpose of this gem when written was mainly for testing and db seeding with faker.

[b264]

I tested this approach with RSpec and it seems that using the module-level approach with @@instances is the only way it will work. The class approach could be added later if needed. RSpec seems to give Unique amnesia when used the other way.

[b264]

This needs to be added to spec/unique/unique_spec.rb instead of here so CI will run this. It looks good otherwise. https://travis-ci.org/b264/unique/jobs/164806377#L165

[b264]

rake or rake default should run the tests

[atomaka]

Fixed and rebased.

[atomaka]

Stateful makes sense, but I also had concerns about that functioning with RSpec.

[b264]

[b264]

released as 0.1.0