Simon Lydell
dc93bdc983
* Extract custom tests from tests/flow/
Approach:
1. Remove all .js files in tests/flow except .snap.js files.
2. Copy over all .js files from tests/ in the flow repo.
3. Go through the diff looking for deletions.
- It was easy to see which deletions were due to changes in the tests
due to updates in the flow repo.
- For the rest of the deletions, I used `git blame` to verify that
they had been added by us since the flow tests were copied over.
This makes tests/flow/ simply a copy of the tests from the flow repo,
making it easier to sync with the upstream flow tests in the future.
* Add a script for syncing the flow tests
* Sync the flow tests
23 lines
561 B
JavaScript
23 lines
561 B
JavaScript
class C {
|
|
constructor() { }
|
|
}
|
|
|
|
class D {
|
|
constructor():number { }
|
|
}
|
|
|
|
// the return type of a constructor overrides the type of the class
|
|
declare class Bar<T> {}
|
|
declare class Foo<T> {
|
|
constructor<U>(iterable: U): Bar<U>;
|
|
}
|
|
(new Foo('x'): Bar<string>); // ok
|
|
(new Foo(123): Bar<string>); // error, number !~> string
|
|
|
|
// also overrides when it returns a different specialization of the same class
|
|
declare class Baz<T> {
|
|
constructor<U>(iterable: U): Baz<U>;
|
|
}
|
|
(new Baz('x'): Baz<string>); // ok
|
|
(new Baz(123): Baz<string>); // error, number !~> string
|