Add basic types to the kernel's asm

[4l0n50]

Sometimes, debugging the kernel code can be extremely painful, only to discover that the issue was caused by a missing DUP(i) or an incorrect SWAP(i). These errors often result in evaluating a function (we don't really have functions, but essentially we do) with an incorrect argument—for instance, passing an address where a boolean was expected. Such errors could potentially be caught easily with a simple type checker.

[0xaatif]

between this and #299, have we considered using a subset of an existing language our ASM code in?

• C
• Rust
• Typescript
• Forth

[0xaatif]

Here's how you might implement e.g PUSH and ADD:

use std::ops::Add;

use tuplez::{ops::Poppable, Tuple}; // 0.14.15

pub fn add<Stack0, Stack1, Stack2, LeftT, RightT, ResultT>(stack0: Stack0) -> Tuple<ResultT, Stack2>
where
    Stack0: Poppable<PopBackElement = RightT, PopBackOutput = Stack1>,
    Stack1: Poppable<PopBackElement = LeftT, PopBackOutput = Stack2>,
    LeftT: Add<RightT, Output = ResultT>,
{
    let (stack1, right) = tuplez::TupleLike::pop_back(stack0);
    let (stack2, left) = tuplez::TupleLike::pop_back(stack1);
    let add = left + right;
    Tuple(add, stack2)
}

pub fn push<Stack0, T>(stack0: Stack0, t: T) -> Tuple<T, Stack0> {
    Tuple(t, stack0)
}

#[test]
fn test() {
    let stack = tuplez::Unit;
    let stack = push(stack, "world");
    let stack = push(stack, String::from("hello"));
    let stack = add(stack);
    let (tuplez::Unit, result) = stack.pop();
    assert_eq!(result, "helloworld");
}