Skip to content

exporting to JS might need some name mangling #24886

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
kevmoo opened this issue Nov 11, 2015 · 4 comments
Closed

exporting to JS might need some name mangling #24886

kevmoo opened this issue Nov 11, 2015 · 4 comments
Assignees
Labels
closed-obsolete Closed as the reported issue is no longer relevant web-js-interop Issues that impact all js interop

Comments

@kevmoo
Copy link
Member

kevmoo commented Nov 11, 2015

From @jmesserly on October 21, 2015 23:40

I recall some issues when the Dart class has static methods that are banned in strict mode like "arguments" "caller" and "callee". Pretty obscure but might need name mangling to expose in JS.

Copied from original issue: dart-lang/js-interop-experimental#198

@kevmoo
Copy link
Member Author

kevmoo commented Nov 11, 2015

From @jmesserly on October 21, 2015 23:40

(filed as a tracking issue after a chat with @jacob314)

@kevmoo
Copy link
Member Author

kevmoo commented Nov 11, 2015

From @jacob314 on October 21, 2015 23:50

We're planning on using JS$ to mangle illegal JS names in dart. Perhaps we should use Dart$ to mangle Dart names

@kevmoo kevmoo added the web-js-interop Issues that impact all js interop label Nov 11, 2015
@jacob314
Copy link
Member

Using Dart$ seems consistent with using JS$. Might be nice if we could think of a short prefix that could be used both ways but I can't think of one.

@jacob314 jacob314 self-assigned this Jul 7, 2016
@jacob314 jacob314 mentioned this issue Jul 8, 2016
19 tasks
@matanlurey matanlurey added the closed-obsolete Closed as the reported issue is no longer relevant label Jun 20, 2018
@matanlurey
Copy link
Contributor

I think we've decided exporting to JS is not on the immediate roadmap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-obsolete Closed as the reported issue is no longer relevant web-js-interop Issues that impact all js interop
Projects
None yet
Development

No branches or pull requests

3 participants