Luke Frisken
Luke Frisken
> * I agree the Debug behavior for the private key in toolkit should be a no-op. I think it would be risky if this ended up in system logs....
perhaps the command line argument should be renamed to `address` to imply that it involves both the ip and the port.
Circles and bounded lines too perhaps?
MIT perhaps? https://github.com/reymond-group/tmap/blob/9aa043dd1af022161048ee0a4b5554ec5e34977f/tmap/recipe/meta.yaml#L45
If tree-sitter adopts an official markdown parser implementation written in Rust, then this could perhaps be used as an embedded parser in a recursive fashion?
@tomhoule I ended up doing this myself in a copy of the class, I'll use it until the pull request is merged :) https://github.com/kellpossible/coster/blob/6aaa3139bef6dec5d50f0a44ea96f13baa663bf8/gui/src/graphql/client.rs
@sstadick thanks for the great tool! I've also used it in https://github.com/conda-forge/staged-recipes/pull/16252 I can see it being useful in other projects too.
I also have a situation where being able to express URLs as regular expressions would be useful
I'll check that soon. From memory I should have about 10 GB available.
> This PR as of now doesn't implement inlayed virtual text, i.e. virtual text in between normal text @sudormrfbin I quite like the inlay hints from https://github.com/simrat39/rust-tools.nvim#inlay-hints