Skip to content

VM should support metadata #4057

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gbracha opened this issue Jul 11, 2012 · 5 comments
Closed

VM should support metadata #4057

gbracha opened this issue Jul 11, 2012 · 5 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
Milestone

Comments

@gbracha
Copy link
Contributor

gbracha commented Jul 11, 2012

Per issue #3214.

@DartBot
Copy link

DartBot commented Sep 6, 2012

This comment was originally written by @mhausner


Set owner to @mhausner.
Added Started label.

@iposva-google
Copy link
Contributor

Removed this from the M1 milestone.
Added this to the M2 milestone.

@DartBot
Copy link

DartBot commented Oct 15, 2012

This comment was originally written by @mhausner


The VM can parse (and ignore) metadata. If mirrors need access to metadata, I plan to evaluate the metadata expressions lazily, when it's actually accessed.

@DartBot
Copy link

DartBot commented Nov 27, 2012

This comment was originally written by @mhausner


Closing this issue. Open a new bug if the VM actually needs to interpret/evaluate the expressions.

@DartBot
Copy link

DartBot commented Nov 27, 2012

This comment was originally written by @mhausner


I said closing, didn't I?


Added Fixed label.

@gbracha gbracha added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. labels Nov 27, 2012
@gbracha gbracha added this to the M2 milestone Nov 27, 2012
@gbracha gbracha mentioned this issue Jun 3, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
Projects
None yet
Development

No branches or pull requests

3 participants