Skip to content

Uniformize class types, maybe #846

@aki-cat

Description

@aki-cat

I know this would change a ton of stuff, but this is pretty confusing to anyone reading the code.

Right now we use three things:

  • steaming -> Class

  • lux.prototype

  • lux.class

I would suggest...making a wrapper of steaming's class using lux's prototype or class. Then we'd ONLY use that wrapper for things, and it'd have features from all of them.

We should have done this a long time ago, tho, now this would take ages to refactor.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions