Chase Gilliam

@Looooong not with bayes, that's not really how it works.

Since `Hasher` is basically a bag of words implementation, it might make sense to rename it as such and make it public and document it as such. Thoughts? @ibnesayeed?

>To overcome this issue in the tests I had to store the original stopwords in an instance variable in the setup method then restore that in the teardown method otherwise...

Yeah, let's start figuring out what needs to be private for 3.0, this will make documentation and maintenance a lot easier.

I'm open to this, but wouldn't know how to do it.

You can marshal to Yaml, which works pretty well for the classifier. We're working on an import/export method at the moment in #174 , but the release date is tbd.

Yeah, I remember #47 pretty well. I agree that it's a bit broken, but I'd like to fix it rather than removing it. Perhaps we can fix it for 3.0,...

Agreed. Let's discuss this further once we make plans for 3.0

@parkr The more I read about this, the more I think a pure Ruby implementation is just going to always give us poor performance. It might make sense to bundle...

Ok. I'll devise a plan tonight and scout out implementations. It'll be good to wrap this one up.