Accepting new baselines.

Previous commit fixes overly aggressive -noImplictAny reporting. In the test case the source
of the error is the 'getAndSet' property that implicitly gets type any. The fact that the setter
then gets type any isn't actually an error.
This commit is contained in:
Anders Hejlsberg 2014-07-31 15:56:00 -07:00
parent bd97ba443a
commit 352a44df3f

View File

@ -1,4 +1,4 @@
==== tests/cases/compiler/implicitAnyGetAndSetAccessorWithAnyReturnType.ts (9 errors) ====
==== tests/cases/compiler/implicitAnyGetAndSetAccessorWithAnyReturnType.ts (8 errors) ====
// these should be errors
class GetAndSet {
getAndSet = null; // error at "getAndSet"
@ -14,8 +14,6 @@
public set haveGetAndSet(value) { // error at "value"
~~~~~~~~~~~~~
!!! Accessors are only available when targeting ECMAScript 5 and higher.
~~~~~
!!! Parameter 'value' implicitly has an 'any' type.
this.getAndSet = value;
}
}