events should be dispatched asynchronously

[millermedeiros]

it was a poor design decision to dispatch the signals as soon as the user calls setHash, events should always be async to avoid headaches (avoid cases where user might not expect something to happen in between).

[millermedeiros]

#48 is also related to this.

[eugene-eeo]

Hi, I just wrote a library called stateless.js which is quite similar but simpler, and I stumbled upon your lib. Asynchronous dispatches can be done via having an event listener on the hashchange event. Those are fired asynchronously on most/all browsers- Firefox, Chrome, Safari (I don't know about IE).

However from my experience testing it is quite tedious; I don't know what kind of asynchronous constructs are offered by QUnit which is used as your test runner if I'm not mistaken. For example in Mocha:

describe(spec, function() {
  it(spec, function(done) {
    hasher.changed.add(function(){
      done();
    });
    hasher.setHash('foo');
  });
});