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

Transpiler: should we support Dart libraries ? #52

Closed
vicb opened this issue Oct 2, 2014 · 1 comment
Closed

Transpiler: should we support Dart libraries ? #52

vicb opened this issue Oct 2, 2014 · 1 comment
Milestone

Comments

@vicb
Copy link
Contributor

vicb commented Oct 2, 2014

As of today each transpiled file as a library statement. The library name is unique and is derived from the file name.

Dart support private members (& functions & variables). Private members start with a "_" prefix.

A private member (/ function / variable) is visible to the entire library (whether it is accessed from the same class or file).

Currently dartanalyzer prints some warnings because "_" prefixed members are accessed from an other file (hence an other library).

What would be the right solution to support this:

  • Support librarystatement in the source code (may be via @LIBRARY('name') if possible),
  • Transform "_" prefixed names,
  • ?

A short term solution could be to avoid "_" prefixed names but we should also have a longer term strategy IMO.

@mhevery mhevery added this to the TBD milestone Oct 14, 2014
@mhevery mhevery closed this as completed Mar 25, 2015
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants