I hope this pitch will come to a (positive) conclusion, so the case for removing "Self or associated type as existential" limitation could be moved forward to implementation and the proposal.
Would hate to see this idea die.
I hope this pitch will come to a (positive) conclusion, so the case for removing "Self or associated type as existential" limitation could be moved forward to implementation and the proposal.
Would hate to see this idea die.
Same here. In fact I'm not quite sure why protocols are treated special anyways. Starting out with Swift I would have expected them to just work fine with generic type syntax. (Actually I also don't understand why you have to do the typealias
dance to make them appear encapsulated in another type, but that's another storyβ¦
I'm having trouble determining the state of this proposal today. This thread references another thread that references this thread, but there really hasn't been any discussion in several months. Did this ever make it to a formal SE?