# Rust 2019: Think Bigger

**URL:** <https://internals.rust-lang.org/t/rust-2019-think-bigger/9003>\
**Category:** Uncategorized\
**Created:** [December 11, 2018, 11:03pm UTC](https://internals.rust-lang.org/t/rust-2019-think-bigger/9003 "2018-12-11T23:03:10Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![matklad](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/matklad/32/12266_2.png) [@matklad](https://internals.rust-lang.org/u/matklad)\
**Post date:** [December 12, 2018, 3:51pm UTC](https://internals.rust-lang.org/t/rust-2019-think-bigger/9003/7 "2018-12-12T15:51:21Z")

</div>

Note also this thread: [[Idea] Cargo Global Binary Cache](https://internals.rust-lang.org/t/idea-cargo-global-binary-cache/9002)

I think it’ll get us 70% of shared [crates.io](http://crates.io) cache with a small amount of implementation & design work.

Fun observation: there’s a desire to add “rlib dependencies” feature to Cargo, to integrate with other build systems and such. This is a huge design space. However, just sharing `target` dir for all `crates.io` work will get us shared cache aspect of rlib dependencies, and is very simple because the layout of target dir is controlled by Cargo and is an implementation detail. Basically, we need to tweak a couple of lines in Cargo to say "if this dep comes from [crates.io](http://crates.io), compile it to `~/.cargo/target`" and not to `./target`.

---

_[View the full topic](https://internals.rust-lang.org/t/rust-2019-think-bigger/9003)._