Is it appropriate to use AtomicReference with a java lambda?

Asked Mar 20 '18 at 22:35

Active Mar 20 '18 at 23:41

Viewed 2,909 times

I often find myself using this idiom:

AtomicReference<MyCoolObject> coolReference = new AtomicReference(new MyCoolObject());

getOptionalValue().ifPresent(presentValue -> {
  coolReference.set(new MyCoolObject(presentValue));
});
return coolReference.get();

Is this a bad habit, or a legitimate use of AtomicReference?

edited Mar 20 '18 at 22:36

shmosel

49,289
6
73
138

asked Mar 20 '18 at 22:35

afspear

What's the point? Why do you need an atomic reference? – shmosel Mar 20 '18 at 22:37
What problem are you trying to solve with that construct? – Philipp Mar 20 '18 at 22:38
FYI, an alternative using method references: `getOptionalValue().map(MyCoolObject::new).ifPresent(coolReference::set)` – shmosel Mar 20 '18 at 22:39
2

Better `return getOptionalValue().map(MyCoolObject::new).orElseGet(MyCoolObject::new);` – fabian Mar 20 '18 at 22:41
@shmosel, Because I can't return the new `MyCoolObject` inside the lambda. – afspear Mar 21 '18 at 14:30
@fabian This looks like a pretty nice alternative. – afspear Mar 21 '18 at 14:31

Is it appropriate to use AtomicReference with a java lambda?

0 Answers0