-
Notifications
You must be signed in to change notification settings - Fork 1.9k
simplify dart 2.0 command line execution #31808
Copy link
Copy link
Closed
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failuresarea-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
Description
Activity
Metadata
Metadata
Assignees
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failuresarea-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
Currently we have numerous options that need to be set when invoking dart 2.0 on the command line.
Would be more ideal if we
Would also be ideal if we could generate a core snapshot of platform binaries and linked it
into the executable instead of the platform binaries. This has the issue of figuring out how
we provide the platform binaries to the front end which requires it for incremental compilations.
(the snapshot has the kernel representation of all the core libraries, maybe the interface to the
FE can be changed to allow dart to specify the platform binaries from the snapshot).