add a destroy method

[davidmarkclements]

it would be nice if we could do explicit cleanup

bloom.destroy() // remove all patterns and clean up any internal refs

[mcollina]

The question for having a bloom.destroy() is what is the state after doing so. Can you still add new patterns to it? If not, why don't you just do bloom = bloomrun()?

[mcdonnelldean]

@davidmarkclements comment on the above?

[davidmarkclements]

I forget my thought process around this - perhaps a bloom.clear() so you can add patterns again

[mcdonnelldean]

So bloomrun.clear() would be nice as long as it but I think it would ultimately be sugar over bloom = bloomrun(). Honestly though, I've yet to come across a time where it made sense to clear down patterns at runtime since the fault from that was usually a big issue.

[mcdonnelldean]

@mcollina Thoughts on this? I still haven't found a use case to be honest.

[mcollina]

So, I'm 👎 , I think we can close this for now. Feel free to reopen this at any time.