rust-memory-container-cs VS silicon

To fix the problem, smart pointer is the go-to, in this case at least. Someone made a cheat sheet for memory containers, and I thought might be useful to share it here.

With Rc, it was failing as I'm using rayon for multi-threaded rendering and Rc is not Sync (that's what I understand from: the Rust memory container cheat-sheet

I agree with you here, but it's disingenuous to claim that the Cell family are not an intentional and necessary part of the design of Rust's ownership system; I would be interested to see any sort of documentation or RFC commentary that implies otherwise. Even a simple 'Rust 101'-style cheatsheet makes it apparent that they're very much a small but necessary part of the whole: https://github.com/usagi/rust-memory-container-cs

There is silicon.nvim that uses the cli tool silicon to export the code as an image (I think there is also an alternative that uses carbon). There is also vim-copy-as-rtf that works only on OSx and Code2RTF.vim that works only on Windows (there was a fork of vim-copy-as-rtf for Linux, but I can't find it). Finally, there is this discussion about alternatives, being one of them to use pandoc and :TOHtml to export the text as RTF

Use Carbon or if you want a program there is silicon

Have you seen https://github.com/Aloxaf/silicon by the way?

Another one in Rust: https://github.com/Aloxaf/silicon

You can use https://carbon.now.sh/ for this!Find the CLI here: https://github.com/mixn/carbon-now-cliAlternative: Silicon (Rust): https://github.com/Aloxaf/silicon

You can follow directions here on how to install it on your system.

Silicon (CLI)