0e65e45e9e
For calls via getters and fields front-end generates MethodInvocation node with interface target pointing to a getter/field. Such target doesn't fully represent what is being called - it should be implicitly chained by call(), so it is incorrect to use such interface target for type propagation. Change-Id: I76198b443474fdcb383671fbc9946b4938a4e1df Reviewed-on: https://dart-review.googlesource.com/c/88260 Auto-Submit: Alexander Markov <alexmarkov@google.com> Reviewed-by: Régis Crelier <regis@google.com> Commit-Queue: Régis Crelier <regis@google.com>
Run Existing Tests ================== See the output of ../tools/test.py --help for how to run tests. See also https://code.google.com/p/dart/wiki/Building#Testing for detailed examples. Create New Tests ================ See comments above factory StandardTestSuite.forDirectory in ../tools/testing/dart/test_suite.dart for the default test directory layout. By default test-file names must end in "_test.dart", but some test suites, such as ./co19, subclass StandardTestSuite and override this default. See comments at the beginning of ../tools/testing/dart/multitest.dart for how to create tests that pass by failing with a known error. For example, ... int x = "not an int"; /// 01: static type warning ... as part of a test will only pass the "--compiler dart2analyzer" test if the assignment generates a static type warning.