Niklas Fiekas

Unfortunately this is not clear without reading the implementation in RocksDB, but it looks like `rocksdb_options_set_merge_operator()` passes ownership: https://github.com/facebook/rocksdb/blob/d17be55aab80b856f96f4af89f8d18fef96646b4/db/c.cc#L2877 So usage in this library seems correct.

Rules 1-3 make a lot of sense to me, and they could be added to the automated linter. Considering an alternative to the proposals ... if we give up on...

Revisiting this and having some doubts ... Regarding ECO: I was hoping we could remove it entirely, and asked around a bit. For all its flaws, people are still using...

Awesome, thanks!

Source code location looks very similar to #3.

Also see https://github.com/ornicar/lila/issues/5074#issuecomment-491870360. As a first step, we should survey software that supports `{[%clk 0:09:57]}` and see how it reacts to `{[%clk 0:09:57.12]}`.

related to #3360

How is it going almost 1 year later?

Emojis are fine, but abusing unicode characters is a terrible way to do text formatting.

Interesting issue. I think it's best/easiest to formally keep the rule that pawn moves to the backrank are always promotions, even if the outcomes of the different choices are indistinguishable*....