server VS lazy-static.rs

I created Server.js https://serverjs.io/ and still use it. It is a wrapper around express:

- With a bunch of middleware included and pre-configured, like body-parser, cookies, Helmet, etc. All express middleware works with Server.js

- async/await routers as expected: get('/users', async (ctx) => {...}); (ctx inspired by Koa)

- Websockets, where messages behave just as another route: socket('message', async ctx => { ... });

I did that! I hope you are not the person who suffered that from me (did you use Picnic CSS a few years back?). So for a newer project I put some setup code that will look for all code snippets with a specific comment and run that with the code after the comment. For generating the website documentation that test bit can be stripped (though I kept it for now).

Example: https://github.com/franciscop/server/blob/master/docs/docume...

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...