fenix VS lazy-static.rs

Rustup works as is. Though note that Nix supplants all such toolchain installers such as Rustup, nvm, etc. I.e. instead of Rustup there is fenix.

Fenix ( https://github.com/nix-community/fenix ) has tooling or picking a specific toolchain or even nightly. You can then build with the following nix code:

Fenix monthly is a new branch similar to the main branch, but only updated on the 1st of every month, for cases where you want to use rust nightly but don't need it to be updated very often.

The issue should be fixed once the nix-vscode-extension and fenix patches are merged. The latter will happen automatically once CI passes.

4. I would suggest Mozilla's Rust overlay or fenix or similar instead of Rustup - that would be more of the "Nix-way" to acquire the toolchain and you can still manage multiple versions. Not sure what the Ruby equivalent is, I don't do Ruby.

To follow along, you'll need a stable Rust toolchain. See the install page for instructions to install rustup for your platform. You should prefer this method to your distribution's package manager. If you're a NixOS freak, I recommend fenix.

Normally lazy_static allows to have "const" code that cant be const https://github.com/rust-lang-nursery/lazy-static.rs

It's an additional crate, but you could try using lazy-static or once-cell and wrap the global value in a RwLock.

lazy_static : A macro for declaring lazily evaluated statics in Rust.

Without understanding the implementation details of lazy_static I figured it would be easier to benchmark it than to dig through its source code.

The templates need to be compiled before use, but this only needs to happen once. We can use lazy_static to ensure this compilation happens the first time the templates are accessed, and then reuse the compiled result for all subsequent access:

Now, the readme examples are tested like everything else.

https://github.com/rust-lang-nursery/lazy-static.rs/blob/mas...