Skip to content
This repository has been archived by the owner on Jul 10, 2023. It is now read-only.

Newtypes instead of monolithic id #117

Open
fkaa opened this issue Feb 28, 2016 · 4 comments
Open

Newtypes instead of monolithic id #117

fkaa opened this issue Feb 28, 2016 · 4 comments

Comments

@fkaa
Copy link
Contributor

fkaa commented Feb 28, 2016

Is there any reasoning for using traits and implementing them onto id rather than creating newtypes such as struct NSString(id)? I've been running into name collisions with the former a lot lately.

@jdm
Copy link
Member

jdm commented Feb 28, 2016

I would be in favour of making this change; @pcwalton can you think of any reason not to?

@jdm
Copy link
Member

jdm commented May 15, 2016

@metajack Any objection here?

@metajack
Copy link
Contributor

This is a question best answered by @pcwalton. It might help in decision making to see a concrete example of how this changes things before and after.

@fkaa
Copy link
Contributor Author

fkaa commented May 15, 2016

I've had some success with this inside my own bindings, and I can definitely see the use for this here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants