Struct Types conforming to protocols, Conforming to protocols that contain associated types in function signatures

I went through the SwiftBaseLibrary and I noticed that numerical base types don’t really conform to a set of their associated protocols that are defined (present but commented out).

I played around with it and noticed that whatever the defined struct type it is (such as RemObjects.Oxygene.System.Double) it cannot be extended to implement the protocol. The compiler would not see the method implementation and always complain it won’t find it. Maybe it has something similar with Protocol Implementation for Silver Struct Types in Extension

Another issue that popped up is that whenever Protocol’s associated type is used as part of its method signature, the compiler again won’t find the implementation when trying to conform to it.

I understand that this is the limitation of the current state of Silver’s compiler front-end, but I am curious - will it be fixed in coming 8.4 release? Then the SwiftBaseLibrary can be improved to match the Apple’s counterpart better.

Yes, known issues that bug me too, and I really hope we’ll be able to address them for 8.4 (if not even for 8.3.95). No promises, but we’ll try our best to make it happen fast.

1 Like