Skip to content

Symbol tables should keep internal properties separate #16868

Closed
@sandersn

Description

@sandersn

Right now symbol tables store things like __call and __construct alongside user-provided symbols. This forces us to mangle/unmangle symbols that start with two underscores. Instead, symbol tables should keep a map of user-provided symbols as before, but also provide optional properties for internals like __call et al.

When the symbol() type becomes available, the symbol table should also include an "dynamic names" map in addition to the "user-provided names" map.

Metadata

Metadata

Assignees

No one assigned

    Labels

    UnactionableThere isn't something we can do with this issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions