First class modules avoid some of the problems with protocols/typeclasses but it seems like it would be more verbose in many cases - what is the state of the art here?
-
-
(BTW Any is mostly implemented with unsafe code tricks under the hood. The only compiler support is the ability to get a runtime type-id, and the library does the rest. It’s very minimal.)
-
That makes sense. Existential types are built-in to Swift, with a fair amount of runtime support (heap allocated copy on write containers, and the whole reified type metadata system)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.