Skip to content

Better type support with components #312

@alexcrichton

Description

@alexcrichton

Currently the way records and variants are supported with components is a bit kludge. All records are a Record and some variants are a Variant but others are "a union of a bunch of types". There's no way to get more static information which is unfortunate.

Ideally what would happen is that when a component was loaded and compiled it would load up and define Python classes for variants/records within the component. These python classes would then be used during conversion to/from C and could be used with isinstance and such. In theory it would also be nice to customize the classes used for use cases like ahead-of-time generated bindings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    component-modelRelated to component bindings generationwasmtime c-apiIssues that require changes in Wasmtime's C API and can't make progress until that's done first.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions