Skip to content

Commit

Permalink
Reimplement specialization for const traits
Browse files Browse the repository at this point in the history
  • Loading branch information
compiler-errors committed Nov 23, 2024
1 parent f5be3ca commit 3644c4a
Show file tree
Hide file tree
Showing 4 changed files with 138 additions and 21 deletions.
122 changes: 108 additions & 14 deletions compiler/rustc_trait_selection/src/traits/specialize/mod.rs
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ use rustc_data_structures::fx::FxIndexSet;
use rustc_errors::codes::*;
use rustc_errors::{Diag, EmissionGuarantee};
use rustc_hir::def_id::{DefId, LocalDefId};
use rustc_infer::traits::Obligation;
use rustc_middle::bug;
use rustc_middle::query::LocalCrate;
use rustc_middle::ty::print::PrintTraitRefExt as _;
Expand Down Expand Up @@ -230,23 +231,26 @@ pub(super) fn specialization_enabled_in(tcx: TyCtxt<'_>, _: LocalCrate) -> bool
/// `impl1` specializes `impl2` if it applies to a subset of the types `impl2` applies
/// to.
#[instrument(skip(tcx), level = "debug")]
pub(super) fn specializes(tcx: TyCtxt<'_>, (impl1_def_id, impl2_def_id): (DefId, DefId)) -> bool {
pub(super) fn specializes(
tcx: TyCtxt<'_>,
(specializing_impl_def_id, parent_impl_def_id): (DefId, DefId),
) -> bool {
// We check that the specializing impl comes from a crate that has specialization enabled,
// or if the specializing impl is marked with `allow_internal_unstable`.
//
// We don't really care if the specialized impl (the parent) is in a crate that has
// specialization enabled, since it's not being specialized, and it's already been checked
// for coherence.
if !tcx.specialization_enabled_in(impl1_def_id.krate) {
let span = tcx.def_span(impl1_def_id);
if !tcx.specialization_enabled_in(specializing_impl_def_id.krate) {
let span = tcx.def_span(specializing_impl_def_id);
if !span.allows_unstable(sym::specialization)
&& !span.allows_unstable(sym::min_specialization)
{
return false;
}
}

let impl1_trait_header = tcx.impl_trait_header(impl1_def_id).unwrap();
let specializing_impl_trait_header = tcx.impl_trait_header(specializing_impl_def_id).unwrap();

// We determine whether there's a subset relationship by:
//
Expand All @@ -261,27 +265,117 @@ pub(super) fn specializes(tcx: TyCtxt<'_>, (impl1_def_id, impl2_def_id): (DefId,
// See RFC 1210 for more details and justification.

// Currently we do not allow e.g., a negative impl to specialize a positive one
if impl1_trait_header.polarity != tcx.impl_polarity(impl2_def_id) {
if specializing_impl_trait_header.polarity != tcx.impl_polarity(parent_impl_def_id) {
return false;
}

// create a parameter environment corresponding to an identity instantiation of impl1,
// i.e. the most generic instantiation of impl1.
let param_env = tcx.param_env(impl1_def_id);
let param_env = tcx.param_env(specializing_impl_def_id);

// Create an infcx, taking the predicates of impl1 as assumptions:
let infcx = tcx.infer_ctxt().build(TypingMode::non_body_analysis());

let specializing_impl_trait_ref =
specializing_impl_trait_header.trait_ref.instantiate_identity();
let cause = &ObligationCause::dummy();
debug!(
"fulfill_implication({:?}, trait_ref={:?} |- {:?} applies)",
param_env, specializing_impl_trait_ref, parent_impl_def_id
);

// Attempt to prove that impl2 applies, given all of the above.
fulfill_implication(
&infcx,

let ocx = ObligationCtxt::new(&infcx);
let specializing_impl_trait_ref = ocx.normalize(cause, param_env, specializing_impl_trait_ref);

if !ocx.select_all_or_error().is_empty() {
infcx.dcx().span_delayed_bug(
infcx.tcx.def_span(specializing_impl_def_id),
format!("failed to fully normalize {specializing_impl_trait_ref}"),
);
return false;
}

let parent_args = infcx.fresh_args_for_item(DUMMY_SP, parent_impl_def_id);
let parent_impl_trait_ref = ocx.normalize(
cause,
param_env,
impl1_trait_header.trait_ref.instantiate_identity(),
impl1_def_id,
impl2_def_id,
&ObligationCause::dummy(),
)
.is_ok()
infcx
.tcx
.impl_trait_ref(parent_impl_def_id)
.expect("expected source impl to be a trait impl")
.instantiate(infcx.tcx, parent_args),
);

// do the impls unify? If not, no specialization.
let Ok(()) = ocx.eq(cause, param_env, specializing_impl_trait_ref, parent_impl_trait_ref)
else {
return false;
};

// Now check that the source trait ref satisfies all the where clauses of the target impl.
// This is not just for correctness; we also need this to constrain any params that may
// only be referenced via projection predicates.
let predicates = ocx.normalize(
cause,
param_env,
infcx.tcx.predicates_of(parent_impl_def_id).instantiate(infcx.tcx, parent_args),
);
let obligations = predicates_for_generics(|_, _| cause.clone(), param_env, predicates);
ocx.register_obligations(obligations);

let errors = ocx.select_all_or_error();
if !errors.is_empty() {
// no dice!
debug!(
"fulfill_implication: for impls on {:?} and {:?}, \
could not fulfill: {:?} given {:?}",
specializing_impl_trait_ref,
parent_impl_trait_ref,
errors,
param_env.caller_bounds()
);
return false;
}

// If the parent impl is const, then the specializing impl must be const.
if tcx.is_conditionally_const(parent_impl_def_id) {
let const_conditions = ocx.normalize(
cause,
param_env,
infcx.tcx.const_conditions(parent_impl_def_id).instantiate(infcx.tcx, parent_args),
);
ocx.register_obligations(const_conditions.into_iter().map(|(trait_ref, _)| {
Obligation::new(
infcx.tcx,
cause.clone(),
param_env,
trait_ref.to_host_effect_clause(infcx.tcx, ty::BoundConstness::Maybe),
)
}));

let errors = ocx.select_all_or_error();
if !errors.is_empty() {
// no dice!
debug!(
"fulfill_implication: for impls on {:?} and {:?}, \
could not fulfill: {:?} given {:?}",
specializing_impl_trait_ref,
parent_impl_trait_ref,
errors,
param_env.caller_bounds()
);
return false;
}
}

debug!(
"fulfill_implication: an impl for {:?} specializes {:?}",
specializing_impl_trait_ref, parent_impl_trait_ref
);

true
}

/// Query provider for `specialization_graph_of`.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,11 +1,31 @@
error: cannot specialize on const impl with non-const impl
error[E0119]: conflicting implementations of trait `Bar`
--> $DIR/const-default-bound-non-const-specialized-bound.rs:28:1
|
LL | / impl<T> const Bar for T
LL | | where
LL | | T: ~const Foo,
| |__________________- first implementation here
...
LL | / impl<T> Bar for T
LL | | where
LL | | T: Foo, //FIXME ~ ERROR missing `~const` qualifier
LL | | T: Specialize,
| |__________________^
| |__________________^ conflicting implementation

error[E0119]: conflicting implementations of trait `Baz`
--> $DIR/const-default-bound-non-const-specialized-bound.rs:48:1
|
LL | / impl<T> const Baz for T
LL | | where
LL | | T: ~const Foo,
| |__________________- first implementation here
...
LL | / impl<T> const Baz for T //FIXME ~ ERROR conflicting implementations of trait `Baz`
LL | | where
LL | | T: Foo,
LL | | T: Specialize,
| |__________________^ conflicting implementation

error: aborting due to 1 previous error
error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0119`.
3 changes: 1 addition & 2 deletions tests/ui/traits/const-traits/specializing-constness.rs
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,7 @@ impl<T: ~const Spec> const A for T {
}

impl<T: Spec + Sup> A for T {
//~^ ERROR: cannot specialize
//FIXME(const_trait_impl) ~| ERROR: missing `~const` qualifier
//~^ ERROR conflicting implementations of trait `A`
fn a() -> u32 {
3
}
Expand Down
8 changes: 6 additions & 2 deletions tests/ui/traits/const-traits/specializing-constness.stderr
Original file line number Diff line number Diff line change
@@ -1,8 +1,12 @@
error: cannot specialize on const impl with non-const impl
error[E0119]: conflicting implementations of trait `A`
--> $DIR/specializing-constness.rs:23:1
|
LL | impl<T: ~const Spec> const A for T {
| ---------------------------------- first implementation here
...
LL | impl<T: Spec + Sup> A for T {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0119`.

0 comments on commit 3644c4a

Please sign in to comment.