mirror of
https://github.com/dart-lang/sdk
synced 2024-09-05 16:41:07 +00:00
b0ecbef3cc
Classes can be instantiated directly, abstractly or indirectly: When [cls] is directly instantiated: This means that at runtime instances of exactly [cls] are assumed to exist. When [cls] is abstractly instantiated: This means that at runtime instances of [cls] or unknown subclasses of [cls] are assumed to exist. This is used to mark native and/or reflectable classes as instantiated. For native classes we do not know the exact class that instantiates [cls] so [cls] here represents the root of the subclasses. For reflectable classes we need event abstract classes to be 'live' even though they cannot themselves be instantiated. When [cls] is indirectly instantiated: This means that a subclass of [cls] is directly or abstractly instantiated. R=sigmund@google.com Review URL: https://codereview.chromium.org/2443953002 . |
||
|---|---|---|
| .. | ||
| _chrome | ||
| benchmark_smoke | ||
| co19 | ||
| compiler | ||
| corelib | ||
| html | ||
| isolate | ||
| kernel | ||
| language | ||
| lib | ||
| standalone | ||
| utils | ||
| light_unittest.dart | ||
| README | ||
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.