---
title: "Comment by Aleksander Lantsov on \"Seqlock-Based Atomic Memory Snapshots\" | Hashnode"
description: "Excellent article, thank you! Why is the last access to the "version" variable in the reader (right after loadLoadFence) done with acquire semantics ("
url: "https://hashnode.com/posts/seqlock-based-atomic-memory-snapshots/64cf7f8a79ecbf244f51df0b/comment/65994bcc0fe390a9f91a3fd1"
---

[Discussion](https://hashnode.com/posts/seqlock-based-atomic-memory-snapshots/64cf7f8a79ecbf244f51df0b)

Comment [Seqlock-Based Atomic Memory Snapshots](https://hashnode.com/posts/seqlock-based-atomic-memory-snapshots/64cf7f8a79ecbf244f51df0b)

[Aleksander Lantsov](https://hashnode.com/@lantalex)

[Jan 6, 2024](https://hashnode.com/posts/seqlock-based-atomic-memory-snapshots/64cf7f8a79ecbf244f51df0b/comment/65994bcc0fe390a9f91a3fd1)

Excellent article, thank you!

Why is the last access to the "version" variable in the reader (right after loadLoadFence) done with acquire semantics (instead of opaque)?

[Andrei Pechkurov](https://hashnode.com/@puzpuzpuz)

[Jan 7, 2024](https://hashnode.com/posts/seqlock-based-atomic-memory-snapshots/64cf7f8a79ecbf244f51df0b/comment/65994bcc0fe390a9f91a3fd1#reply-659a78e05a246ab4fe9092fd)

Thanks for the feedback.

As for the last getAcquire, I think you're right. Considering the prior loadLoadFence, it can be changed to getOpaque.