Skip to content

Latest commit

 

History

History
49 lines (33 loc) · 2.7 KB

DESIGN.md

File metadata and controls

49 lines (33 loc) · 2.7 KB
Raw

Design

This directory contains design notes and prototypes of Go bindings for Component Model interfaces.

Exports

Export Bindings for Resource Types

For each exported resource type, in addition to constructors, methods, and static functions, a component must import and export a number of functions to manage the resource lifecycle.

Example

For an exported resource water in package/interface example:foo/bar, a component imports the following administrative functions:

  • resource-new: initialize a resource handle for a given rep (concrete representation). Called by the component before a resource value is returned by an exported function.
    • Import: [export]example:foo/bar [resource-new]water
    • Params: i32 rep (in C bindings, this is a pointer to the representation)
    • Results: i32 handle
  • resource-rep: return the underlying representation of a handle. Can only be called by the component instance that created the original resource.
    • Import: [export]example:foo/bar [resource-rep]water
    • Params: i32 handle
    • Results: i32 rep (in C bindings, this is a pointer to the representation)
  • resource-drop: drops an owned handle to a resource. If the resource has zero loans, the destructor (below) will be called.
    • Import: example:foo/bar [resource-drop]water
    • Params: i32 handle
    • Results: none

In addition, the resource destructor is exported:

  • dtor: destructor, implemented by user code
    • Export: example:foo/bar#[dtor]water
    • Params: i32 rep (in C bindings, this is a pointer)
    • Results: none
    • Notes: the

Similarly, a function is exported for each resource method (e.g. drink and spill)

  • Export: example:foo/bar#[method]water.drink (implemented by user code)
  • Export: example:foo/bar#[method]water.spill (implemented by user code)

Post-Return

Note: as of v0.1.0, this package does not support post-return functions. See #118 for more information.

For each exported function that returns allocated memory, there is a post-return function called by the Canonical ABI machinery to allow the component to free the allocation(s).

The post-return function name is cabi_post_ followed by the fully-qualified function name. For example, the WIT function example:foo/bar#echo returning a string would have a post-return function named cabi_post_example:foo/bar#echo.

The post-return function has the form of (func (param flatten_functype($ft).results)), where the arguments is a flattened representation of the function results.