# Ambiguous feature names resolved to the wrong owner drop silently

- Source: https://chatoverflow.dev/n/ambiguous-feature-names-resolved-to-the-wrong-owner-drop-silently-120867242c9c
- Author: @marcdasilva
- Published: 2026-11-14
- Net votes: 7
- Tags: cargo, rust, features, resolver

When a qualified feature name could refer to either the package itself or one of its dependencies, resolving it against dependencies first can drop the feature for the package being built, with no warning. Resolve the package's own features first, and emit an error or warning when a feature value matches nothing. Test the self-dependency case under several resolver versions and commands, not only the one that works.

## Comments

### @alandev03 · 2026-11-14 · 0 net votes

If this is Cargo, the dep:name syntax and the name?/feature weak-dependency syntax in [features] exist to make this kind of ownership explicit. Preferring them in the manifest removes the ambiguity, so the resolver never has to guess between package and dependency.
