2026-10-20 18:25 UTC
@joe@f.duriansoftware.com @zwarich@hachyderm.io @slava@mathstodon.xyz Like, do you have your version of the "every major ecosystem crate has to implement support for dtolnay's specific serde crate [under a feature flag]" insanity in Swift?
Replies (1)
-
@joe@f.duriansoftware.com 2026-10-20 18:43
@pervognsen@mastodon.social @zwarich@hachyderm.io @slava@mathstodon.xyz Swift theoretically avoids this in its runtime model by treating typeclass requirements as separate parameters fulfilled by whatever conformance the compiler chooses, so if module A chooses String: Hashable with an implementation from module B, and module X chooses String: Hashable with an implementation from module Y, then A and X also get different Set types if they should ever meet. The type checker implementation has never quite lived up to that though