Thanks! It’s actually pretty hard to implement the names in an enum or other static mechanism because some names are prefixes of others. e.g. “circle” and “circle.fill”. What type is ‘.circle’ that will be acceptable as a symbol name and also allow further suffixes? Difficult, but not impossible 😀

The “simple” approach is to have names like .circle and .circleFill, which several libraries have done. But I’d like to use periods in the names, just like the real symbol names (tokens that start with digits would need a leading underscore though).

I have found some code that does it the more complex way on github, but it only supports sf symbols v1. I want to build upon that technique and make a better version, but it’s not really a good use of my time. Using the data I’ve gathered to build Adaptivity I should even be able to add availability annotations so that the compiler would warn about using iOS 14 images in iOS 13 code paths. And warn about deprecated names in iOS 14 code paths. It would be a pretty complex project but, honestly, it is getting harder and harder to resist working on it 😬