Skip to content

Expose fewer public types #241

@qinsoon

Description

@qinsoon

Currently mmtk-core exposes a lot of modules/types/methods/fields as public. Some are careless decisions. This brings the burden to us that some internal refactoring would end up changing the bindings as well. We should do a systematic pass and revisit each public item carefully, and only expose what is necessary.

  • Ideally a binding should only need to use API functions we provide.
  • We should only expose types that are used in those API functions.
  • We should hide details in a module, and only expose certain types from a module.
  • We should try not expose fields.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions