# Concerns about making \`resolver = "2"\` the default in 2021 edition

**URL:** <https://internals.rust-lang.org/t/concerns-about-making-resolver-2-the-default-in-2021-edition/14684>\
**Category:** language design\
**Created:** [May 12, 2021, 7:43am UTC](https://internals.rust-lang.org/t/concerns-about-making-resolver-2-the-default-in-2021-edition/14684 "2021-05-12T07:43:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bjorn3](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/bjorn3/32/2736_2.png) [@bjorn3](https://internals.rust-lang.org/u/bjorn3)\
**Post date:** [May 12, 2021, 8:33am UTC](https://internals.rust-lang.org/t/concerns-about-making-resolver-2-the-default-in-2021-edition/14684/2 "2021-05-12T08:33:31Z")

</div>

> [@weiznich](#):
>
> I cannot see how this statement is true for the `resolver = "2"` , as using the new resolver is nothing that is contained to a specific crate. It applies to the whole dependency tree and therefore forces the behaviour down to all dependencies. In my opinion this violates that the decision of migrating to a newer edition as a "private one" that a crate can make without affection others.

A crate doesn't force it down to all of its dependencies. It applies to a workspace. If one of your dependencies overrides the resolver, it doesn't affect you or the dependencies of said dependency when you don't opt into it. This is the same for profile settings or `.cargo/config.toml`.

---

_[View the full topic](https://internals.rust-lang.org/t/concerns-about-making-resolver-2-the-default-in-2021-edition/14684)._
