Summary:
clippy complains with
```
non-binding `let` on a future
consider awaiting the future or dropping explicitly with `std::mem::drop`
for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#let_underscore_future
`#[warn(clippy::let_underscore_future)]` on by default
```
Because the future we are not awaiting comes from `tokio::spawn`, it is still executing. Use `std::mem::drop` to make the intent of ignoring the handle explicit while satisfying clippy.
Reviewed By: yancouto
Differential Revision: D43468794
fbshipit-source-id: 9da8fe940e00c3043fdfba7d25c8add94ca6818e
Mononoke is a next-generation server for the Mercurial source control
system, meant to scale up to accepting
thousands of commits every hour across millions of files. It is primarily
written in the Rust programming language.
Caveat Emptor
Mononoke is still in development. We are making it available now because we plan to
start making references to it from our other open source projects.
The version that we provide on GitHub is omitting some functions.
This is because the code is exported verbatim from an internal repository at Facebook, and
not all of the scaffolding from our internal repository can be easily extracted. The key areas
where we need to shore things up are:
Support for running thrift based apis.
Production metadata SQL support (e.g. something like a MySQL backend). We provide sqlite in OSS for now.
Production blobstore storage backends (e.g. something like S3). We provide SQL (on sqlite) and File System backends currently in OSS.
Linux is Mononoke's primary target plaform with OSS CI also running on MacOS. Other Unix-like OSes may be supported in the future.
Subsystem Docs
Most of our documentation is in internal systems, however a few subsystems have in-repo markdown docs available:
2a4d191a78