Named type parameters

I’ve not following closely, but one thing I’d like to inject:

I don’t think we want names to automatically become part of the public API. This gives an opportunity – if type parameter names must “opt-in” to being nameable, we can check for conflicts with associated types and the like.


Did your experiment yield any results?

No, I stopped working on it after @nikomatsakis pointed out that traits would have to opt-in anyway

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.