Remove warnings about types—because we fixed them!

Author: chriskrycho

README.md

@@ -127,52 +127,31 @@ landing in TypeScript itself.
 [existing typings]: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/ember
 
 We are hard at work (and would welcome your help!) [writing new
-typings][ember-typings] for Ember and the surrounding ecosystem, which can give
-correct types for Ember's custom object model and things which build on it (e.g.
-ember-data). If you'd like to try those out, please see instructions in [that
-repo][ember-typings]!
+typings][ember-typings] for Ember and the surrounding ecosystem. If you'd like
+to try those out, please see instructions in [that repo][ember-typings]!
 
 [ember-typings]: https://github.com/typed-ember/ember-typings
 
 Here is the short list of things which do *not* work yet in the version of the
 typings published on DefinitelyTyped.
 
-### New modules API
-
-Note: the new modules API is not yet supported by the official typings (which
-are distinct from this addon, though we install them). We do have experimental
-support for them in the [ember-typings] repository, and it works quite well!
-
 ### Some `import`s don't resolve
 
 You'll frequently see errors for imports which TypeScript doesn't know how to
-resolve. For example, if you use `htmlbars-inline-precompile`:
+resolve. For example, if you use Ember Concurrency today and try to import its
+`task` helper:
 
 ```typescript
-import hbs from 'htmlbars-inline-precompile';
+import { task }  from 'ember-concurrency';
 ```
 
 You'll see an error, because there aren't yet type definitions for it. You may
-see the same with some addons as well. These won't stop the build from working;
-they just mean TypeScript doesn't know where to find those.
+see the same with some addons as well. **These won't stop the build from
+working;** they just mean TypeScript doesn't know where to find those.
 
 Writing these missing type definitions is a great way to pitch in! Jump in
 \#topic-typescript on the Ember Slack and we'll be happy to help you.
 
-### `extends` gives errors
-
-You'll see quite a few errors like this when calling `.extends()` on an existing
-Ember type:
-
-> Class 'FooController' incorrectly extends base class 'Controller'.
-> Type '{ bar(): void; }' has no properties in common with type 'ActionHash'
-
-This is a symptom of the current, out-of-date types. The new typings we're
-working on will solve these.
-
-In the meantime, note that your application will still build just fine even with
-these errors... they'll just be annoying.
-
 ### Type safety when invoking actions
 
 TypeScript won't detect a mismatch between this action and the corresponding
@@ -199,31 +178,6 @@ Likewise, it won't notice a problem when you use the `send` method:
 this.send('turnWheel', 'ALSO-NOT-A-NUMBER');
 ```
 
-### Type safety with `Ember.get`, `Ember.set`, etc.
-
-When you use `Ember.get` or `Ember.set`, TypeScript won't yet warn you that
-you're using the wrong type. So in `foo()` here, this will compile but be
-wrong at runtime:
-
-```typescript
-Ember.Object.extend({
-  urls: <string[]> null,
-  port: 4200,  // number
-
-  init() {
-     this._super(...arguments);
-     this.set('urls', []);
-  },
-
-  foo() {
-    // TypeScript won't detect these type mismatches
-    this.get('urls').addObject(51);
-    this.set('port', '3000');
-  },
-});
-```
-
-
 ### The type definitions I need to reference are not in `node_modules/@types`
 
 By default the typescript compiler loads up any type definitions found in