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

private members should not expose the VMs mangling mechanism. #9285

Closed
floitschG opened this issue Mar 19, 2013 · 5 comments
Closed

private members should not expose the VMs mangling mechanism. #9285

floitschG opened this issue Mar 19, 2013 · 5 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.

Comments

@floitschG
Copy link
Contributor

private members should not expose the VMs mangling mechanism.

From the mailing-list (slightly modified):

--- mylib.dart
lib myLib;
class A {
  noSuchMethod(InvocationMirror invocation) => print(invocation.memberName);
}

--- myTest.dart
import 'mylib.dart';
main(){
  final my = new A();
  my._a;
}

--- console
_a@0x3e0efa04

The noSuchMethod should get "_a" and not "_a@0x3e0efa04".

@gbracha
Copy link
Contributor

gbracha commented Mar 25, 2013

This is, I believe, distinct from the issues we get with minification etc. Here, the VM is exposing implementation details that should be completely hidden from the developer.

@iposva-google
Copy link
Contributor

Removed Priority-Medium label.
Added Priority-Unassigned label.

@gramster
Copy link
Contributor

Issue #10524 has been merged into this issue.

@ghost
Copy link

ghost commented Jan 8, 2014

Set owner to @rmacnak-google.

@rmacnak-google
Copy link
Contributor

r38143


Added Fixed label.

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, FFI, and the AOT and JIT backends.
Projects
None yet
Development

No branches or pull requests

5 participants