d39f6bc82e
Summary: This is a follow-on from D8014913 (Make in-memory manifests load lazily), addressing jsgf's review comments. I've made the following stylistic changes: 1. Use `impl Future` for all private APIs instead of `BoxFuture` (making use of `Either` instead of boxing where possible). 2. Use Rust 1.26 style `match` statements with inferred `ref` and `&` whenever possible. 3. Rework the logic in `MemoryManifestEntry::save` to not need `filter_map`. 4. Remove `future::result` and exploit `impl IntoFuture for Result` where possible to reduce code 5. Improve a couple of comments Reviewed By: jsgf Differential Revision: D8209186 fbshipit-source-id: c759ad8894fc25616dc6a291d46c487191f96382 |
||
|---|---|---|
| async-compression/src | ||
| asyncmemo/src | ||
| blobrepo | ||
| blobstore | ||
| bookmarks | ||
| bookmarks_old/src | ||
| bundle2-resolver/src | ||
| bytes-ext | ||
| cache-warmup/src | ||
| changesets | ||
| cmds | ||
| common/pylz4/src | ||
| docs | ||
| eden_server/src | ||
| filenodes | ||
| futures-ext/src | ||
| hgcli | ||
| hgproto | ||
| hooks/src | ||
| hooks_old/src | ||
| mercurial | ||
| mercurial-bundles/src | ||
| mercurial-types | ||
| metaconfig/src | ||
| mononoke-types | ||
| py_tar_utils | ||
| repoinfo/src | ||
| revset/src | ||
| server/src | ||
| sshrelay/src | ||
| storage | ||
| tests | ||
| vfs/src | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| rustfmt.toml | ||
Mononoke
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 early stages of development. We are making it available now because we plan to start making references to it from our other open source projects such as Eden.
The version that we provide on GitHub does not build yet.
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:
- Full support for a standard
cargo build. - Open source replacements for Facebook-internal services (blob store, logging etc).
The current goal is to get Mononoke working on Linux. Other Unix-like OSes may be supported in the future.