public interface TwoLongReference extends net.openhft.chronicle.core.values.TwoLongValue, Byteable
long values stored in bytes, providing mechanisms for getting, setting,
and manipulating them with various memory ordering effects.
This interface extends TwoLongValue to add the ability to back
the two long values with a Bytes store. This is used for off-heap memory
or memory-mapped file storage.
Concrete implementations of this interface are responsible for managing the storage and retrieval mechanisms
of the two long values in byte format.
Notable methods inherited from TwoLongValue include:
TwoLongValue.getValue2() - Retrieves the second long value.TwoLongValue.setValue2(long) - Sets the second long value.TwoLongValue.getVolatileValue2() - Retrieves the second long value with volatile semantics.TwoLongValue.setVolatileValue2(long) - Sets the second long value with volatile semantics.TwoLongValue.addValue2(long) - Atomically adds the given amount to the second long value.TwoLongValue.compareAndSwapValue2(long, long) - Atomically sets the second long value if it is equal to the expected value.
Additionally, as an implementation of Byteable, the classes implementing this interface must provide
mechanisms to back the two long values with byte storage.
Implementations can also include additional behaviors or optimizations not specified in this interface.
Byteable,
TwoLongValueaddAtomicValue2, addValue2, compareAndSwapValue2, getValue2, getVolatileValue2, setOrderedValue2, setValue2, setVolatileValue2addAtomicValue, addValue, close, compareAndSwapValue, getValue, getVolatileValue, getVolatileValue, isClosed, setMaxValue, setMinValue, setOrderedValue, setValue, setVolatileValueaddress, bytesStore, bytesStore, lock, maxSize, offset, tryLockCopyright © 2023. All rights reserved.