Kristian Dalgård

The bind helper being called twice is expected behavior and only causes problems when the previous binding isn't unbound properly before each subsequent call.

Here's another idea: `unbind` accidentally runs _before_ `bind` does, which would explain why `Nexus.remove(this)` returns false – it can't be removed from the global list, because it hasn't been added...

I wonder whether `view.onViewDestroyed` sometimes runs before `view.onViewReady`? If the view is destroyed immediately, is the `unbind` callback run right away when registered? In that case, the value of `view.isRendered`...

Still wish I had a test case ;)

To muddle the image, `list.add` and `list.remove` will both trigger a Tracker flush.

Have we established exactly which hook is responsible for running `unbind`? Is it `onRefreshed`, `onDestroyed`, or `onInvalidate`?

I've solved this by redefining the `softRemovable` behaviour. It's only a small change. In the new version, when applying the behaviour, a modifier object can be passed as an argument....

+1 @rhyslbw, the workaround is working fine for me, but you still need to add the package name to your `.meteor/packages` file.

I'm pretty sure they do – there's no integration between Atmosphere and GitHub.

I'm thinking something like this: ```es6 const _myFun => (arg1, arg2, arg3) => { ... }; export default const myFun = (...args) => { const shouldCurry = args.length < _myFun.length...