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

Resolution error if getter and setter are not in the same library #4386

Closed
lrhn opened this issue Aug 7, 2012 · 7 comments
Closed

Resolution error if getter and setter are not in the same library #4386

lrhn opened this issue Aug 7, 2012 · 7 comments
Labels

Comments

@lrhn
Copy link
Member

lrhn commented Aug 7, 2012

Have two files:
-- vmcrash1-inc.dart ---

library("foo");

int get x() => 42;
-- vmcrash1.dart ---
import("vmcrash1-inc.dart");

int set x(int v) {}

main() {
 x++;
}


and run the VM on vmcrash1.dart. This generates a seg-fault.

@DartBot
Copy link

DartBot commented Aug 7, 2012

This comment was originally written by @mhausner


I am looking at getters and setters, so I can take a look.


Set owner to @mhausner.
Added Accepted label.

@DartBot
Copy link

DartBot commented Oct 3, 2012

This comment was originally written by @mhausner


This is probably caused by the same bug as issue #4946.

@DartBot
Copy link

DartBot commented Oct 4, 2012

This comment was originally written by @mhausner


Update:

This no longer crashes the VM, but it does not find the getter in the library. Here's a simpler version:

=== blib.dart ====
library blib;

int get x => 42;
==== b.dart ====
import "blib.dart";

int set x(int v) {}

main() {
  print(x);
}
=======

If the setter is commented out in b.lib, we find the getter in blib.dart. If it's not commented out, we fail to find the getter.


Changed the title to: "Resolution error if getter and setter are not in the same library".

@iposva-google
Copy link
Contributor

Matthias, is this still an issue?

@DartBot
Copy link

DartBot commented May 29, 2013

This comment was originally written by @mhausner


I will add a test to find out.

@iposva-google
Copy link
Contributor

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

@DartBot
Copy link

DartBot commented Apr 21, 2015

This comment was originally written by @mhausner


Fixed in r45316


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
Projects
None yet
Development

No branches or pull requests

3 participants