[FEA]: Inconsistent template parameter in thrust::complex operators

[srinivasyadav18]

Is this a duplicate?

• I confirmed there appear to be no duplicate issues for this request and that I agree to the Code of Conduct

Area

Thrust

Is your feature request related to a problem? Please describe.

The template parameter in thrust::complex operators w.r.t to the arguments are in consistently used.
For instance -

template <typename T0, typename T1>
__host__ __device__ typename detail::disable_if<
  detail::or_<detail::is_same<T0, T1>, detail::not_<detail::is_arithmetic<T1>>>::value,
  complex<typename detail::promoted_numerical_type<T0, T1>::type>>::type
operator-(const T0 &x, const complex<T1> &y);

The type T1 should actually be T0.

Describe the solution you'd like

Replalce T1 with T0 in detail::is_arithmetic<T0>

template <typename T0, typename T1>
__host__ __device__ typename detail::disable_if<
  detail::or_<detail::is_same<T0, T1>, detail::not_<detail::is_arithmetic<T0>>>::value,
  complex<typename detail::promoted_numerical_type<T0, T1>::type>>::type
operator-(const T0 &x, const complex<T1> &y);

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Hi @srinivasyadav18!

Thanks for submitting this issue - the CCCL team has been notified and we'll get back to you as soon as we can!
In the mean time, feel free to add any relevant information to this issue.

[jrhemstad]

Thanks @srinivasyadav18. Are you still thinking you'd like to take care of this?

[srinivasyadav18]

@jrhemstad Yes. I have a PR coming up right-away.