Bugfix for typealias/associatedtype conflict.
Pre-release
Pre-release
One protocol's typealias
will collide with another protocol's associatedtype
in very ugly ways. This is why for now we will have ResourceObject.ID
and ResourceObject.Id
(both equally valid ways of referring to a ResourceObject
's Identifying type.