abstract casts and dynamic field access

[nadako]

abstract A(Dynamic) from Dynamic to Dynamic {}

class Main {
    static function main() {
        var a:A = {};
        a.test; // A has no field test
    }
}

Is this too crazy?

I got that while working on making node.js url externs. Its URL objects have this field:

@:optional var query:EitherType<String,Dynamic<String>>;

It contains either a string or a dynamic object parsed from that string, depending on the argument given to the parse function. I suppose it's designed to allow field access to it in pure-js.

[nadako]

Also I wonder if this is related:

abstract E<T1,T2>(Dynamic) from T1 to T1 from T2 to T2 {}

class Main {
    static function main() {
        var a:E<Dynamic<String>,String> = {};
        var b:Dynamic<String> = a; // E<Dynamic<String>, String> should be Dynamic<String>
    }
}

[Simn]

I don't get what you mean here, A has no field test so naturally this fails. If you want to access on the underlying type you can add @:forward.

[nadako]

Yeah but A is supposed to implicitly convert to Dynamic which allows field access.

[Simn]

That's not how abstract cast and field access interact.

[nadako]

What about the second case?