grape's Introduction

Grape Virtual Machine (GrapeVM)

(WIP) A light, simple and efficient runtime implemented in Rust.

Features

Extensibility: Designed to be easily extendable, allowing the addition of custom modules and function objects.
Cross-Platform: Made with Rust, works on a wide range of platforms like Linux, macOS and Windows.
Memory Management: Includes a memory management system to efficiently allocate and deallocate memory as needed during program execution.

grape's People

Stargazers

Watchers

grape's Issues

Improve docs

Support OOP/Classes

Modules should support 0 or many class definitions and each class should be unique at the Runtime context.

struct Module {
  ...
  pub classes:   BTreeMap<Rc<str>, Class { name, fields, methods }>,
  pub functions: BTreeMap<Rc<str>, Function>,
  ...
}

- Each class must have a unique new/initializer method.

Should all classes come before the functions? Or it's better to have a CLASS/STRUCT/FUNCTION tag before reading it?

A class can be stored as a Box<[Value]> at the heap where every field will have an offset/identifier, this can be done by a compiler or as a VM transformation.

Both fields and methods in a class can be private or public. I believe this also implies on adding accessors for module functions.