Kevin Millikin
385f8fb054
1. A --platform flag is added to dart to give a path to a Kernel binary for the platform libraries (as produced by building the runtime_kernel target). 2. This binary is used for bootstrapping. Since it contains libraries other then the VM's bootstrap libraries, they are also loaded. 3. The frontend does not send any library with a dart: import URI scheme. Note that it does not (yet) prune the canonical name table, which will contain a lot of unnecessary names used for internal linkages in the platform libraries. 4. There is a single dependency in the platform libraries on the script: _getMainClosure in dart:_builtin. This is patched after the script is loaded. BUG= R=ahe@google.com, kustermann@google.com, vegorov@google.com Review-Url: https://codereview.chromium.org/2786083002 .
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.