Skip to content

Object properties: move to Pharo #3

@MarcusDenker

Description

@MarcusDenker

I think we should move the poperties API to Pharo, using a SharedVariable.

With the already unified API, this would mean that some subclasses (who use it a lot) re-implement the properties to not need a per object table. (see e.g. AST nodes or CompiledMethod)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions