FFI API

[liz3]

FFI Api for dictu.

What's Changed:

Adds a FFI api which allows a C abi to easy extend dictu with native functions.

• It works by providing a header(dictu-include.h) which contains all macros which might be useful for external users, although of course theres the chance i missed something.
• The header replaces the compiler entry with a void pointer to avoid having to copy all its structs
• The header contains function pointers for all the required functions from the vm, which are loaded at runtime automatically(dictu_internal_ffi_init), this avoids the user having to link against dictu or duplicate function definitions.
• It also contains a mechanism to ensure that function pointers can safely be loaded with a versioning system.
• The pr also adds support for two things:
  1. Invoking functions on a abstract without self as 0 arg, this is because the remote ffi function should only receive the actual function arguments, the 0 argument is the FFIInstance
  2. Adding properties to abstract which was a quick edit in the vm but might be useful for external modules.

Type of Change:

• Bug fix
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Housekeeping:

• Tests have been updated to reflect the changes done within this PR (if applicable).
• Documentation has been updated to reflect the changes done within this PR (if applicable).

[liz3]

im not sure why the docs fail but maybe its the empty links, but all other tests pass.
thats good

[Jason2605]

Apologies been busy, I def will get round to this, thank you so much!

Be good to get your eyes too if you have any spare time @briandowns 🙂

[liz3]

Apologies been busy, I def will get round to this, thank you so much!

Be good to get your eyes too if you have any spare time @briandowns 🙂

All good no stress

[briandowns]

Can you add new line characters to any file that don't have them?

[briandowns]

I love this. Very very cool. Few things:

• Can we add the shared object libraries to the .gitignore?
• How are would it be to use Dictu as an embedded language now with the shared objects?
• Even thought it's FFI, I was curious aabout folks thoughts on naming the module "external" or something similar.

I can't wait to get started using this!

[liz3]

I love this. Very very cool. Few things:

* Can we add the shared object libraries to the .gitignore?

* How are would it be to use Dictu as an embedded language now with the shared objects?

* Even thought it's FFI, I was curious aabout folks thoughts on naming the module "external" or something similar.

I can't wait to get started using this!

Can we add the shared object libraries to the .gitignore?

Uh if you can help me build the test libs with the runner sure. Since they are required for the tests.

How are would it be to use Dictu as an embedded language now with the shared objects?

Im not entirely sure what you mean by embedded here, as in including shared objects into a binary? Im a tad confused.

Even thought it's FFI, I was curious aabout folks thoughts on naming the module "external" or something similar.

We can do that idm about the name at all.

[Jason2605]

It's probably worth adding this to the include directory within src, that way people may find it easier rather than it being in the examples directory

[Jason2605]

This is really really awesome!!! Thank you so much for working on this!! I'm gonna merge this in but left a little comment about moving / copying one file that any of us can pick up at some point (not massively urgent)