Stepan Koltsov

Maybe it could at least show some progress while doing it. Because it is not clear, is it even doing anything while the window looks just like this:

The problem in my case is that we use userspace filesystem which contains terabytes of files (rust project root is not FS root, but a small part of it). I...

**Update**: I cleaned CLion caches and problem disappeared: CLion no longer tries to scan the whole filesystem. Yet, diagnostics of what's going on during "Getting Rust stdlib" would be helpful.

Merged the part about `encoded_varint64_len`. Can you please rebase and confirm miri is no longer an issue?

OK, if this is still an issue, some benchmark is needed. Smaller machine code does not mean code is faster. (Project is not very well maintained now, so long responses,...

I think changes in `.github/workflows/ci.yml` should be reverted.

Also we don't need a separate crate for test. Instead, code should be customized for single test file within test suite.

There are options like [tokio_bytes](https://docs.rs/protobuf-codegen/latest/protobuf_codegen/struct.Customize.html#method.tokio_bytes) to change codegen behavior. Change to `BTreeMap` should done similarly.

Working on this PR, merging parts of this, this is why it shows merge conflict now.

OK, merged. Now need to either merge to stable branch or create new stable branch.