Triggered events -- Only use reset like paginated collection?

[bryanspears]

Backstory -- Displaying a filtered subcollection using a select-view. It's quite slow when you filter 300+ models and noticeable with 200+ models. Firing add/remove events for each model change is the source of the problem as select-view re-renders the entire options list each add/remove/reset.

The fix is simple, and I'm currently using it (replace the two foreach add/remove cases with one reset) and it works perfectly. I'll work on the tests later.

Any feedback? Reasons for using add/remove over a single reset? Otherwise, I hope to have a PR soon.

[wraithgar]

It would be interesting to see this demonstrated w/ a larger collection that's rendered, using the resets. I know @legastero uses this heavily (or did in the recent past) and would probably have a good take on this.

I'm not opposed in theory, just would need to see that it doesn't detriment any more than what it's trying to fix.