Ways to reduce compilation time incurred by highly overloaded functions (==)?

Hi there, I have a question about reducing compilation times of highly overloaded functions (==). Specifically, about the potential impact of reducing the number of overloads in a build using the Swift 6.3 compiler. These questions build off of this post( Type checker impact of reducing occurences of highly overloaded functions (==)? ), which could be good context. I’m looking for guidance on three approaches we have evaluated for reducing the compile-time cost associated with a very large numb...