These instructions were used because it was more painful to implement
lookups and function calls for operators with the AST body compiler.
This is less of a hurdle now with the list compiler, and since these
instructions are extensive and involve a lot of copy-paste, they have
been removed to help with code bloat.
They may be reintroduced in the future for optimization purposes.
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
* obj::Bool builtin type is used for truthiness and decision-making
* Branches are compiled and seem to be working for basic integer
comparison
* Updated version of Shredder to what is current as of writing
* CheckTruth VM instruction that will explicitly set the condition flag
* Probably some other stuff
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
* Currently, scopes are only allowed to look at their locals and the
globals. Inner functions cannot refer to values in their parent
functions. This will change eventually.
* Scope lookup is split between globals and locals. Locals are defined
in a scope if they are explicitly assigned to.
* i.e. `a = foo` will treat `a` as a local in the current scope if
it appears anywhere in that scope. This does not extend to
setattrs; `a.b = foo` will not trigger `a` into being a local var.
* `Package` objects are no longer returned from the compiler - instead,
a user function is returned.
* Other various changes and renames
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
* VM Signals are used by running functions to dictate whether a function
should return, or if it should call another function. These signals
can be injected at any time allowing for user functions to inject
themselves at runtime.
* obj::Method is gone since it's not being used yet.
* Obj impls must implement as_any(&self) -> &dyn Any now. This allows
for UserFun and NativeFun to be explicitly cast (among other things,
in the future).
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
* Code is compiled into a vm:📦:Package which contains the
executable code, the constants, and the local name mappings.
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
* Variables were previously named "Local"s because they described a
local variable - however, this is kind of a misnomer because it
handles globals as well. This has been changed pretty much everywhere
when appropriate (hopefully).
* Renamed obj/names.rs to obj/reserved.rs, freeing up the "names" module
for the new Names handle
* Renamed obj/locals.rs to obj/names.rs, see above
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
A vector of instructions and constants can now be decompiled as text on
the terminal to give an idea of what the VM is doing.
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
* Upon entering a new body, the local scope variables are collected.
* VM instruction PushLocal now uses a `Local` value instead of a `Sym`
value
* Compilation of a new AST body will implicitly create a new scope
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
* Basic are a more linear way of representing code. Thunks beget basic
blocks, which beget vectors of instructions.
* Basic blocks are also being flattened into a vector of instructions
(hopefully, no tests done yet)
* OH yeah locals can be collected too (but currently are not being
collected in the compiler, that should come soon)
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
Some instructions are currently implemented. Others are not. This is
mostly just a checkpoint so I can implement lexical name definitions.
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
While I like the idea of having a runtime completely decoupled from the
syntax and compiler, I don't think this is that big of a project for
that to be necessary or even useful yet.
Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
