Equivalent of ObjC class `load` in Swift

[costinAndronache]

AFAIK it's recommended that you rely on global lazy initializations,

Pitch: `@globalConstructor`

This is something we've been trying to avoid in the language. There's a couple reasons for that: The first is that global constructors have an inherent ordering problem. Global constructors often end up having dependencies on other global constructors, and solving that well is sort of a pit of complexity, especially without elaborate toolchain support. The second is that global constructors are inherently very brittle because by design they precede all normal user code (other than other …