Ariel Mashraki

Thanks for reporting this issue @tatsuya6502. I'm not sure if having something like `TeeWriter` should be part of this crate. However, I think we can start with updating the README,...

Thanks for your contribution @stbuehler ! before I review it, can you please add an example to the example directory, so I'll be able to run it?

I think the general idea is good and useful. I’ll give it more attention tomorrow morning.

I didn't have any progress on this, but I'm in favor of adding it, since it's actually needed for other uses cases as well, like #17.

Hey @andrewstucki, thanks for your contribution. I'm not sure I want to add these extra files just for one variable. What do you think about adding something like this: ```go...

Any update on this @andrewstucki?

Hey @jawang35, Thanks for bringing up this issue. I actually started implementing this a few years ago, and it made this package much complicated and no more stateless, unlike today....

I like it. Also, there are several more aliases in `angular-filter` that I like to add: - [`contains`](https://github.com/a8m/angular-filter#contains) -- `some` - [`unique`](https://github.com/a8m/angular-filter#unique) -- `uniq` - and all the other booleans...

I like it. great job We need to take this logic and copy it to [angular-filter](http://github.com/a8m/angular-filter). it just makes more sense.

Hey @tom10271, Thanks for opening this issue. I agree that the README is pretty poor. All the filters have proper documentation in [angular-filter](http://github.com/a8m/angular-filter) repo. for example, [afterWhere](https://github.com/a8m/angular-filter#afterwhere). If you're willing...