remove redundant assignment of isDestroyed
[BUGFIX release] Fix #3681.

`Em.arrayComputed` is not presently compatible with lazy CPs. There are a few
issues.

1.  To keep refs up to date, observers stay around as long as the object does.
2.  Those observers can repopulate the cache, but when they do so they fail to
    add dependent keys when the cache was empty.

This commit works around 2. by not removing them in the first place.
Essentially the semantics for `ArrayComputedProperty`s differ from standard
`ComputedProperty`s with regards to laziness.

These observers need to be managed better.  Probably the right thing to do, now
that `recomputeOnce` is no longer necessary, is to:
  1. Fix `Em.computed.sort` to not use `recomputeOnce`;
  2. Fix `Em.arrayComputed` to return a proxy to the cached value;
  3. Teardown array observers when the deps count hits 0.

This will give reduce computed properties semantics much closer to regular
computed properties.  There are two important points to note about this
suggestion:

1.  The cached values would still update synchronously.  This can be improved
    with a lazy array implementation and @wycats's skiplist strategy.
2.  The semantics of an array computed would change such that existing refs
    would only be kept up to date as long as the cache had not been invalidated.
    This is probably fine: the current behaviour is not promised in the
    documentation anywhere and it would be pretty bad practice to keep
    references around rather than `Ember.get`ing them.
[BUGFIX beta] Added assert mismatched template compiler version.

See #3728. Using an old version of Ember to precompile templates
can result in an unusual error when trying to render a component
in block form, e.g.

```
  {{#my-component}}Hello{{/my-component}}
```

This commit adds an assert to give the user more information
as to what's going on.
Docs: Fix link in handlebars text field API

Currently, this link was returning a 404 response. It should be
relative to the /api/classes path. This change fixes the link.
[BUGFIX beta] Add spec for unhandled exception being logged by Test.adapter.exception

The changes in exception handling introduced in
cf0caa04f625067ec3b4629acdec12c8517df94e made a test assertion in an
existing test obsolete, since it wasn't called anymore.

This commit adds a spec for Test.adapter.exception being invoked, when
an exception is not handled.
[DOC] What a Hampster is?
[BUGFIX beta] Enumerable#any no longer returns false if NaN is matched

Fixes #3736
Merge pull request #3735 from thenickcox/fix_handlebars_link

Docs: Fix link in handlebars text field API
Merge pull request #3705 from pangratz/fix/spec_for_unhandled_exception

[BUGFIX beta] Add spec for unhandled exception being logged by Test.adapter.exception
Correct GH issue URL referenced in blockHelperMissing comments
[BUGFIX beta] {{partial}} helper now works with bound params

{{partial name}} will look up `name` on
the present template context and render the partial
whose name is the present value of `name`. If `name`
changes, the partial gets re-rendered. If name is
falsy, nothing gets rendered. If name refers to a
non-existent template/partial, the same assertion you'd
see if you'd explicitly passed in an invalid template/partial
name in string form will fire.
improved instrumentation.subscribe docs
[BUGFIX beta] Use RegExp.test() for Ember.computed.match.

After a bit of research I believe that `RegExp.test` is quite a bit
faster and results in clearer code (as it returns a boolean instead of a
match array).

Quote from the MDN article on `String.match`:

    If you need to know if a string matches a regular expression regexp, use
    regexp.test(string).

Supporting research:

http://jsperf.com/test-vs-match-regex
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/test
ttp://stackoverflow.com/a/10940138/1157494

Resolves #3746.
Merge pull request #3756 from rjackson/use_regexp_test_for_computed_match

[BUGFIX beta] Use RegExp.test() for Ember.computed.match.
[DOC beta] Fix typo in name for `customEvents`

As noticed by @alexdiliberto in http://git.io/KD6Lzg
[DOC beta] Update enumerable.js
[BUGFIX beta] Ensure aliased {{with}} blocks are not shared.

Use prototypal inheritance to ensure that the keywords available within
a `{{#with}}` block are not leaked outside the `{{/with}}`.

Added tests to prevent regression.

Closes #3652.
Closes #3753.

(@twokul && @hjdivad && @rjackson)
Merge pull request #3745 from machty/bound-partial-helper

[BUGFIX beta] {{partial}} helper now works with bound params
[DOC beta] adds more docs to transitionTo
Fix documentation error

Was `Context` and should be `Contact`