Skip to content

Separate FFI from Alumet core #96

@TheElectronWill

Description

@TheElectronWill

What

Extract the FFI (which allows to define plugins as dynamic libraries) from the alumet crate to another one. Only keep the minimal amount of FFi-related features in the core.

Why

Many reasons:

  • FFI is unstable and likely won't be stabilized soon, because no one needs it for now. Keeping it in the core prevents it from going to v1.0.0.
  • Moving to a separate crate would give it an independent version number and pace.
  • Easier to delegate the work to someone else, because it won't involve modifying the core.
  • Easier to experiment new things related to FFI without breaking the core of Alumet.

Metadata

Metadata

Labels

A:core ⚙️area: Alumet core libraryT:code-qualitytype: Improvement of the codebase

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions