You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.P1A high priority bug; for example, a single project is unusable or has many test failures
Currently we have numerous options that need to be set when invoking dart 2.0 on the command line.
Need to specify platform binaries location
Need to specify location of the front end snapshot
Would be more ideal if we
generated the front end snapshot as part of the sdk
linked in the platform binaries into the executable
auto located the front end snapshot from the sdk
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).
The text was updated successfully, but these errors were encountered:
a-siva
added
the
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
label
Jan 9, 2018
We have gotten rid of the requirement to specify the following options in order to run in 2.0 mode, we are down to being able to do 'dart --preview_dart_2 myapp.dart' to be able to run in 2.0 mode.
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.P1A high priority bug; for example, a single project is unusable or has many test failures
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).
The text was updated successfully, but these errors were encountered: