Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Changing Deserializable to require init? as oppose to init #62

Open
peymanmortazavi opened this issue Jul 20, 2016 · 1 comment
Assignees

Comments

@peymanmortazavi
Copy link

peymanmortazavi commented Jul 20, 2016

When deserializing, I might pass a completely irrelevant object to init of a deserializable object and they have to handle it. having the option to return nil and say there are not enough information to initialize this object would be great specially since <-- operator does return an optional anyway.

┆Issue is synchronized with this Asana task

@peymanmortazavi peymanmortazavi changed the title Changing Deserializable to require init? as oppose to init Request: Changing Deserializable to require init? as oppose to init Jul 20, 2016
@isair
Copy link
Owner

isair commented Jul 20, 2016

Makes sense. I will commit this change soon.

@isair isair self-assigned this Jul 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants