Skip to content
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

Determine whether print is part of dart:core #4608

Closed
iposva-google opened this issue Aug 20, 2012 · 3 comments
Closed

Determine whether print is part of dart:core #4608

iposva-google opened this issue Aug 20, 2012 · 3 comments
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. P1 A high priority bug; for example, a single project is unusable or has many test failures

Comments

@iposva-google
Copy link
Contributor

There is the constant confusion whether print is part of core or not. Currently each implementation defines this differently. See for example issue #3638.

@iposva-google
Copy link
Contributor Author

cc @mhausner.
cc @peter-ahe-google.

@lrhn
Copy link
Member

lrhn commented Sep 4, 2012

Print is in the core library now.
It does "something reasonable", usually involving calling toString on its input.

@lrhn
Copy link
Member

lrhn commented Sep 4, 2012

Added Fixed label.

@iposva-google iposva-google added Type-Defect P1 A high priority bug; for example, a single project is unusable or has many test failures area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. labels Sep 4, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

2 participants