Static methods about gop HOT 3 OPEN

Introducing static methods at this point seems reasonable, especially since Go+ already has the concept of classfile.

However, the "right cast" appears somewhat peculiar. It seems to create more problems than it solves.

For instance, in this example:

func OrigT.rcast(arg1 OrigT) DestT
func DestT.cast(arg1 OrigT) DestT // It can be defined like this, right?

var v1 OrigT
v2 := DestT(v1) // OrigT.rcast(v1) or DestT.cast(v1)?

It's unclear which method v2 := DestT(v1) would call. At least we can't tell just from this line of code. I assume there would be a priority, but that still wouldn't mitigate the confusion introduced by the "right cast".

from gop.

Introducing static methods at this point seems reasonable, especially since Go+ already has the concept of classfile.

However, the "right cast" appears somewhat peculiar. It seems to create more problems than it solves.

For instance, in this example:

func OrigT.rcast(arg1 OrigT) DestT
func DestT.cast(arg1 OrigT) DestT // It can be defined like this, right?

var v1 OrigT
v2 := DestT(v1) // OrigT.rcast(v1) or DestT.cast(v1)?

It's unclear which method v2 := DestT(v1) would call. At least we can't tell just from this line of code. I assume there would be a priority, but that still wouldn't mitigate the confusion introduced by the "right cast".

eg.

func T.rcast(v T) int // convert T to int

from gop.

parser/printer: Static methods (#1848)

from gop.