Actorable vs. ClassBehavior: should the later be removed?

[ktoso]

Before we went down the path of codegen we had ClassBehavior as well.

Should we remove it now that "the way" for classes and more "has state" is the Actorables?

[yim-lee]

If ClassBehavior doesn't offer any distinguishing feature(s) then I would vote for its removal. (I didn't know it exists...)

[ktoso]

Sounds like we could remove it :-)

WDYT @drexin ?
Since Actorable exists this has a lesser benefit and perhaps just adds to the confusion?

[ktoso]

I guess good to remove it.

[drexin]

Hey, sorry... completely missed the ping here. I think there's not much use to it with Actorable being a thing. Too many ways to define actors will just confuse people.

[ktoso]

Yup, sounds like a plan :)