TypeScript/tests/cases/conformance/expressions/assignmentOperator
Matt McCutchen cc1c2ab6b2 Go back to the old narrowing algorithm (pre #26143) and avoid #26130 by
skipping narrowing if the old algorithm produces a type to which the
assigned type is not assignable.

This also means we'll no longer narrow for erroneous assignments where
the assigned type is not assignable to the declared type.  This is the
reason for the numericLiteralTypes3 baseline change.

Fixes #26405.
2018-08-17 21:35:03 -04:00
..
assignmentGenericLookupTypeNarrowing.ts Have getAssignmentReducedType use the comparable relation instead of 2018-08-01 23:26:17 -04:00
assignmentLHSIsReference.ts Update tests 2016-09-21 16:03:51 -07:00
assignmentLHSIsValue.ts Update tests 2016-09-21 16:03:51 -07:00
assignmentTypeNarrowing.ts Go back to the old narrowing algorithm (pre #26143) and avoid #26130 by 2018-08-17 21:35:03 -04:00
compoundAdditionAssignmentLHSCanBeAssigned.ts Add snapshot of compiler sources 2014-07-12 17:30:19 -07:00
compoundAdditionAssignmentLHSCannotBeAssigned.ts Add snapshot of compiler sources 2014-07-12 17:30:19 -07:00
compoundAdditionAssignmentWithInvalidOperands.ts Add snapshot of compiler sources 2014-07-12 17:30:19 -07:00
compoundArithmeticAssignmentLHSCanBeAssigned.ts Add snapshot of compiler sources 2014-07-12 17:30:19 -07:00
compoundArithmeticAssignmentWithInvalidOperands.ts Add snapshot of compiler sources 2014-07-12 17:30:19 -07:00
compoundAssignmentLHSIsReference.ts Add snapshot of compiler sources 2014-07-12 17:30:19 -07:00
compoundAssignmentLHSIsValue.ts Update tests 2016-09-21 16:03:51 -07:00