Autocomplete does not work for List elements and abstract classes

[RedHead90]

var list:List<Something> = new List();

for(element in list) {
    element. //no code tips here
}

This does not work, because the List.iterator() method returns a exemplar ListIterator. If I change it to an Iterator, then the autocomplete starts working.

@:forward
abstract AbstractWrapper<T>(T) from T to T {
    public inline function new(value:T) this = value;
}

var obj:AbstractWrapper<Something> = new Something();
obj. //no code tips here

These problems are not present if you enable the checkbox Use compiler in the SDK settings.

[mayakwd]

Iterators already fixed in the EAP build, second issue still reproducing.

[EricBishton]

Tweaking the code a bit gives some of the functionality:

package ;

@:forward
abstract AbstractWrapper<T>(T) from T to T {
    public inline function new(value:T) this = value;
    public function extraFunctionality() : T {return this;}
}

class TestIssue772 {
    public function new() {
        var obj:AbstractWrapper<String> = new String();
        obj.      //no code tips here
    }
}

As you can see, functions defined within the AbstractWrapper are available for completion. However, I think the disconnect is that we don't process the to functionality when we walk the class hierarchy looking for candidates.

[RedHead90]

Sorry for my English. I`m really looking forward to this fix. And now it has become even more critical, because in Haxe 4 preview versions, Null<T> has also become an abstract type. Now he looks exactly like my example and autocomplete does not work even for such trivial things as Null<String>.

[EricBishton]

Will be in release 1.2.