vtable abstraction of some kind. traits? oop? polymorphism? interfaces?

[babariviere]

That will be good if we have traits like in rust.

[andrewrk]

Indeed, perhaps we need an abstraction that provides a vtable of some kind. Traits seem pretty reasonable. I still need to think it all over before deciding on a particular abstraction.

One thing I want to do before closing this issue is create a GUI application with widgets and stuff. That's the classic use case for OOP so we can test out how well the vtable abstraction works.

[kyle-github]

Structural polymorphism? I.e. if I have:

`
const A = struct {
foo: u16;
}

const B = struct {
bar: A;
baz: f32;
}
`

Can you pass a pointer to B where a pointer to A was needed?

[kyle-github]

It looks like if you allow fields to be reordered by the compiler, then this would not be possible. That will prevent a certain kind of polymorphism from working. This is fine as long as it is explicitly stated somewhere. See the points in issue #307.