Relative and absolute imports don't resolve to the same path

[Hixie]

A common case we see is this:

// main.dart
import 'package:app/bar.dart';

class A { }

void main() {
  assert(new A().runtypeType == test().runtimeType); // fails
}

// bar.dart
import 'package:app/main.dart';

A test() {
  return new A();
}

This fails because the import in bar.dart resolves to a different path than what we first run, so there's two copies of main.dart floating around. It results in extremely confused developers.

See e.g. flutter/flutter#17575.

[kevmoo]

There are existing discussions on how main(...) should ever be in the lib directory, right?

[leafpetersen]

Is this a dup of #33076 ?

[leafpetersen]

See also #32601 ?

[Hixie]

both of those look like the same thing, yup.

[lrhn]

This is an instance of what #33076 should fix, so closing as duplicate of that.