Open dabrahams opened 1 year ago
Looks like we made this API as well :/
Loosening constraints is not API-breaking
Even if it were, we could just provide extra overloads taking [Any]
instead of [any CustomStringConvertible]
and map the existing overloads to the new ones, so I think it'd be fine?
Description
Instances like this (and many others) are creating needless constraints. Everything is convertible to a string; a conformance to
CustomStringConvertible
(which is fine) just means the user wanted to customize the default result. This anti-pattern should be removed.Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of
swift --version ; uname -a
)No response