Ian Hobson
Ian Hobson
OK thanks, I'll have a go at implementing it then =)
I took a quick look, and it seems like there's a potential issue with the idea. For a `Peekable` iterator we need to implement `next()` to either return the peeked...
I had the same question in #147 - there's no way to `peek()` with the current API, but I've had success with wrapping `Lexer` in a custom peekable iterator which...
@progician As a starting point, you could try something like: ```rust struct Peekable, peeked: Option, } impl { fn new(source: &'source str) -> Self { Self { lexer: Token::lexer(source), peeked:...
Some groundwork for this was done in #290. I didn't go any further because I'd like to understand more about how debugging might one day work before making any guarantees...
Hey @ales-tsurko 👋 I'm interested in using wasm as the primary extension runtime too, I like the idea of a library of platform-independent precompiled modules that can be easily pulled...
Oh interesting I see.. Something to keep in mind for the wasm-y future =)
I think you could implement this as a separate library, e.g. `koto_wasm`, so in a koto script you'd do something like: ```coffee import wasm x = wasm.compile 'foo.wasm' x.exports.bar() ```...
Hey @chaosprint, it hadn't occurred to me, but why not? I'll get to it as soon as I can, probably sometime next week.
@pascalkuthe Ok, I checked Neovim's behavior and it uses double spaces to separate the lines, which seems like a reasonable idea to me. Here's the example from above using this...