@scanon I would like to understand your thoughts on whether this may (despite best efforts) significantly hinder adoption to the point of being counterproductive.
Adding swift-numerics as a dependency pinned to a non-tagged commit has been considered risky in some of the teams that I've worked with. It could certainly be the case that folks in these teams (myself included) are not appreciating the stated goals and what means in terms of practice.
My personal estimator (but one that I've known my peers to share) for the 'health of a package' includes factoring in whether warnings introduced by recent (stable and non-beta) versions of the Swift toolchain are being addressed. That does not seem to be the case for the commit for the last tagged release (image attached, I just downloaded the last release and opened it with Xcode 16.2). No stated goals could change the fact that this is the case well into the public release of Swift 6.
I understand that a fix for this has already been made in main, but if the timeline for releasing said fix is hindered significantly for whatever reason, it does downgrade the package's health for me in consideration as an external dependency.
For my own versioned OSS Swift packages, I personally do feel that it is a sign of poor maintenance, and have been criticized for it by external contributors.
On a slightly tangential note, but relevant to the warnings in the screenshot: I personally have gripes with the Swift 6 language mode introducing this as a warning. IIRC there's been some discussion on allowing folks to turn this warning off, I'm not sure whether those discussions have materialized.
