> Looks pretty good. I see someone has been reading "The Error Model" by Joe > Duffy, eh? Yes! It was a _huge_ inspiration. In fact, I wasn't sure what err

> Looks pretty good. I see someone has been reading "The Error Model" by Joe > Duffy, eh? Yes! It was a _huge_ inspiration. In fact, I wasn't sure what error handling mechanism to use until I read the article. > Something like "public_send" or "define_method". And maybe show runtime > reflection capabilities, if Inko has them. Good call, I'll note this down. Technically this is possible at the moment, but it's not exactly user friendly. Regarding your list of suggestions, I agree that having those would be nice, and I'll see how I can best add those. The state of the standard library can best be described as "very young". For example, only recently did I manage to add enough building blocks to build a testing standard library, and one of the next goals is to make sure everything is tested before adding more. Benchmarks aren't available yet because I think it's too early. FFI is planned, but not yet supported.