Yorick Peterse

https://github.com/inko-lang/tree-sitter-inko implements everything necessary at a base level. https://github.com/nvim-treesitter/nvim-treesitter/pull/6549 adds support for NeoVim, which requires a bunch of NeoVim-specific queries. For Helix I'm not sure what the process is, but...

@alexaandru Thanks! :smile:

To add to the above: the tree parser should (ideally) be based on the pull parser.

I'm working on this in https://github.com/inko-lang/inko/pull/710. So far it's turning out to be a tad tricky: pull parsing lends itself well to data formats that aren't very strict (e.g. they...

Another issue arises when introducing support for parsing a `Read` type: this greatly increases the number of places where an error might occur. Even something as simple as peeking a...

I'm getting the same results on my laptop (which also runs Arch linux): ``` bash [yorickpeterse@tuxbook in ~]$ rvm gemset use pry Using /home/yorickpeterse/.rvm/gems/ruby-1.9.3-p125 with gemset pry [yorickpeterse@tuxbook in ~]$...

@banister No, it seems to be working fine with the latest version of Pry. Closing this issue as it has been resolved.

For [Inko](https://gitlab.com/yorickpeterse/inko): > Does this implement a custom allocator or rely on native allocation? Both. That is, it uses Rust's built-in allocator but managed objects (= those allocated by the...

@pliniker I imagine this being less of an issue on newer architectures, but I wouldn't be surprised if the problem persists on mobile/embedded devices (e.g. those running ARM). Even if...

If it helps: Inko's VM loop uses some `unsafe` code, but this is mostly to work around some weird borrow checking limitations. This is because the VM will borrow a...