piccolo icon indicating copy to clipboard operation
piccolo copied to clipboard

An experimental stackless Lua VM implemented in pure Rust

Results 49 piccolo issues
Sort by recently updated
recently updated
newest added

Been going through my open source projects which I've been neglecting and figured I should write something here about where I am with this project. Unfortunately I'm no longer working...

I just published a crate named luster, not realizing that there was a Rust program of that name. I dont mind trying to change my crate if you might still...

The static string key is frequently written when creating a standard library, so I can write it simply.

Hello, I have just been pointed to this repository, as I'm currently investigating scripting languages accessible from rust that would support builtins that return `-> impl Future` (and thus have...

``` [zaoqi@zaoqi-pc lua]$ lua -i lang.lua Lua 5.3.5 Copyright (C) 1994-2018 Lua.org, PUC-Rio > [zaoqi@zaoqi-pc lua]$ ............../luster/target/debug/luster -r lang.lua Error: ThreadError(BadCall(TypeError { expected: "function", found: "nil" })) ``` https://gitlab.com/the-language/the-language/blob/d13341505075cb8cc4fa9b23212fd9c9932bc556/core/pure/lua/lang.lua

I believe that a "sufficiently smart compiler" would compile this String::new to the same machine code as the existing implementation. (Pretty sure rustc isn't that compiler, though.) Could retain the...

I've started to have a play with `luster` to see how it might fit into another project. I was wondering about adding some of the `table` functions, but notice that...

These changes allow `piccolo` to compile for `wasm32-unknown-unknown` target.

Also changed print() to use space instead of tab between arguments since this is how the official lua implementation seems to work. Should also note that I'm new to Rust...

I noticed that the crate lua-patterns already did all the hard work for us here, so this is mostly just adding that. We could do the same for some other...