Problem: hardcoded Rust-type based errors are problematic

[pumpkindb]

Problem: hardcoded Rust-type based errors are problematic

[yrashk]

Chat dump

Yurii Rashkovskii @yrashk 12:59
thinking out loud. what if errors were value-only closures in a reverse order?
like
[… however much you want to include.. “Error description” CODE]
this way code would always be on the top of the stack, and depending on the code you would know how to process it
or
[[… however much you want to include…] “Error description” CODE] to keep the form regular (always 3 elements)
this way we can send errors, process errors in PumpkinScript, etc.
Or [ “Error description” [… however much you want to include…] CODE] perhaps is even better in terms of order of importance
if you want to return an error error, simply 2DROP
this gives me another idea
another form for EVAL, EVAL!
will push [“" [] 0] if everything went fine, actual error otherwise
this would require some gutting changes in the interpreter, though
but likely not terribly hard

[yrashk]

Done in #57