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

Add memoizing toString()/hashCode() #426

Merged

Conversation

sav007
Copy link
Contributor

@sav007 sav007 commented Apr 18, 2017

Closes #420

Similar result to what AutoValue Memoized generates.

@hzsweers

@ZacSweers
Copy link
Contributor

So some of us were discussing this and think that the synchronized block is actually overkill, and that the cost of re-calculating is probably less than the cost of the synchronized lock. I'd say just keep it simple and skip it. @digitalbuddha thoughts?

@digitalbuddha
Copy link
Contributor

I agree skip it.

@sav007
Copy link
Contributor Author

sav007 commented Apr 19, 2017

@digitalbuddha @hzsweers any comments?

@sav007 sav007 merged commit c257a55 into apollographql:master Apr 19, 2017
@sav007 sav007 deleted the feature-420/memoized-hashcode-tostring branch April 19, 2017 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants