Skip to content

configurable function exports #331

@radkomih

Description

@radkomih

Currently, all exported functions are hard-coded in runtime.go. However, there is a need for a configurable approach to determine what should be exported and when.

Examples:

  • building wasm runtimes for benchmarking, which exports additional functions, whereas this is not necessary for development or release builds.
  • building wasm runtimes from templates with different consensus modules (aura, babe) configured.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    🆕 New

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions