Can you provide an example or docs for extending a Qt class? E.g. A simple example that extends qt_widgets::main_window::MainWindow and overrides closeEvent? This is commonly needed to intercept closing of a window.

(I assume this is not implemented per rust-qt/ritual#26, I'll just leave this open because a simp

It might be worth considering adding simd-json to the TechEmpower benchmarks:

https://github.com/TechEmpower/FrameworkBenchmarks/blob/cfbbf5d11143c96851620eb1aeaf3c2893e862c9/frameworks/Rust/actix/src/main.rs#L23

To make this really worthwhile #121 would be good.

suggested by @pickfire

We have to clean out the examples-bak directory into either real code or throw it out entirely.

Does it spark joy?

It's bad UI design to have required option flags on a command-line tool. In fact, the documentation for Python's in-stdlib argument parsing library explicitly teaches people to avoid it.

This...

rustig [FLAGS] [OPTIONS] --binary <FILE>

...should be this...

rustig [FLAGS] [OPTIONS] <FILE>

Requiring --binary or -b before what could be a positional argument just makes the c

Right now it looks like this:

It would be more readable when using the usual colors red and green for the changed lines.

See for example GitHub: https://github.com/nix-community/nixpkgs-fmt/pull/110/files

![Screenshot from 2019-08-26 15-37-55](https:

Currently we use RwLock<Option<DBAndColumns>> in order to:

• support closing/upgrading (see restore) a RocksDB kvdb database.
• [hold a read lock](

Hi, Is there is a minimal working example (i.e Hello World Nginx) so we can start from that point?

Thank you.

Could be useful to have a benchmark to measure how many events can be fired per second.

We could think of running one bench with only DummyEvent and another bench with StartRound and EndRound in sequence.

Keep in mind all events end up in the in-memory timeline and we shouldn't allocate too much for a benchmark.