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

Delete local copies of LongAdder/Striped64 in favor of java.util.concurrent.atomic.LongAdder #3183

Open
mjd507 opened this issue Jun 15, 2018 · 2 comments

Comments

@mjd507
Copy link

mjd507 commented Jun 15, 2018

in the package com.google.common.hash and com.google.common.cache,
some files like LongAddable, LongAddables, LongAdder, and Striped64 are the same.

@mjd507 mjd507 changed the title find two same Striped64.java files in guava, is this intentional ? Find some same files in guava , is this intentional ? Jun 15, 2018
@kluever
Copy link
Member

kluever commented Jun 15, 2018

Yep, we don't want them to be public APIs, so the only way to use them in both packages is to make 2 copies.

What I didn't realize is that LongAdder actually made its way into Java8. I suspect we can delete our copies of Striped64 and LongAdder in our Java8 branch. @lowasser ?

@kluever kluever changed the title Find some same files in guava , is this intentional ? Delete local copies of LongAdder/Striped64 in favor of java.util.concurrent.atomic.LongAdder Jun 15, 2018
@lowasser
Copy link
Contributor

I think this would break GWT/J2CL.

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

5 participants