Compilation error when implementing `From` using a concrete associated type from another crate

[stormshield-kg]

I have the following files from 2 crates:

// dep/src/lib.rs

pub trait Wrapped {
    type WrappedType;
}

pub struct W3;
pub struct S3;

impl Wrapped for S3 {
    type WrappedType = W3;
}

// main/src/lib.rs

use dep::Wrapped;

struct W;
struct S;

impl Wrapped for S {
    type WrappedType = W;
}

struct W2;
struct S2;

impl Wrapped for S2 {
    type WrappedType = W2;
}

// This works
impl From<<S2 as Wrapped>::WrappedType> for W {
    fn from(value: W2) -> Self {
        todo!()
    }
}

// This doesn't work
impl From<<dep::S3 as Wrapped>::WrappedType> for W {
    fn from(value: dep::W3) -> Self {
        todo!()
    }
}

Currently I have the following error:

error[E0119]: conflicting implementations of trait `std::convert::From<W>` for type `W`
  --> main/src/lib.rs:23:1
   |
23 | impl From<<dep::S3 as Wrapped>::WrappedType> for W {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `core`:
           - impl<T> std::convert::From<T> for T;

I expected that <dep::S3 as Wrapped>::WrappedType would be resolved to a single type like <S2 as Wrapped>::WrappedType>, and that the code would compile.

Context

I'm using dep::S3 and W as the inputs of a proc-macro, and I would like to generate impl From<dep::W3> for W inside the proc-macro, but without mentioning dep::W3 explicitely.

Meta

rustc --version --verbose:

rustc 1.70.0-nightly (0599b6b93 2023-04-01)
binary: rustc
commit-hash: 0599b6b931816ab46ab79072189075f543931cbd
commit-date: 2023-04-01
host: x86_64-unknown-linux-gnu
release: 1.70.0-nightly
LLVM version: 16.0.0

[clubby789]

This might be related to #102728, as

the orphan check does not look into associated types as it has to run before we are able to do so.

[stormshield-kg]

Since the type W is local and explicit, there shouldn't be any problem with the orphan rule check.

[clubby789]

What I mean is that the conflicting impls check also likely runs before looking into associated types is possible