a4f323ce9c
Suggest creating unary tuples when types don't match a trait When you want to have a variadic function, a common workaround to implement this is to create a trait and then implement that trait for various tuples. For example in `pyo3` there exists ```rust /// Calls the object with only positional arguments. pub fn call1(&self, args: impl IntoPy<Py<PyTuple>>) -> PyResult<&PyAny> { ... } ``` with various impls like ```rust impl<A: IntoPy<PyObject> IntoPy<Py<PyAny>> for (A,) impl<A: IntoPy<PyObject, B: IntoPy<PyObject> IntoPy<Py<PyAny>> for (A, B) ... etc ``` This means that if you want to call the method with a single item you have to create a unary tuple, like `(x,)`, rather than just `x`. This PR implements a suggestion to do that, if applicable. |
||
---|---|---|
.. | ||
as_expression.current.stderr | ||
as_expression.next.stderr | ||
as_expression.rs | ||
do_not_apply_attribute_without_feature_flag.rs | ||
do_not_apply_attribute_without_feature_flag.stderr | ||
feature-gate-do_not_recommend.rs | ||
feature-gate-do_not_recommend.stderr | ||
incorrect-locations.rs | ||
incorrect-locations.stderr | ||
simple.current.stderr | ||
simple.next.stderr | ||
simple.rs | ||
stacked.current.stderr | ||
stacked.next.stderr | ||
stacked.rs | ||
supress_suggestions_in_help.current.stderr | ||
supress_suggestions_in_help.next.stderr | ||
supress_suggestions_in_help.rs | ||
type_mismatch.current.stderr | ||
type_mismatch.next.stderr | ||
type_mismatch.rs | ||
unstable-feature.rs | ||
unstable-feature.stderr |