Vlad Mihalcea The definition of nonstrict rw is pretty vague:

Read and write access (non-strict). Data may be added, removed and mutated. The non-strictness comes from the fact that locks are not maintained as tightly as in READ_WRITE, which leads to better throughput but may also lead to inconsistencies.

So this definition allows both dirty reads as well as stale reads. On the other hand, the implementation should offer as much consistency as possible without lowering throughput, so ideally only short window of stale reads (I consider dirty reads quite nasty). Your statement 'there is no locking' is more an implementation detail. Evict is said to 'Forcibly evict an item from the cache immediately without regard for transaction isolation', but it does not say it removes any locks or other metadata.