Controller-aware wrappers around the most-used :ets operations.

ETS itself is BEAM-level shared state -- the operations are atomic per-row but multiple operations don't compose atomically. The classic example is read-modify-write:

v = :ets.lookup_element(t, :counter, 2)
:ets.insert(t, {:counter, v + 1})

Two processes running this concurrently can both read the same v, then both write v + 1, losing one update. Under bare :ets, this race depends on scheduler timing -- rare in tests, common at scale. With Lockstep.ETS.lookup_element/3 + Lockstep.ETS.insert/2, every operation is a sync point, so the scheduler can interleave between A's lookup and A's insert. The race surfaces on the first iteration that picks that interleaving.

Usage

Either call Lockstep.ETS.* directly, or let Lockstep.Rewriter rewrite :ets.* calls in your code under use Lockstep.Test, rewrite: true or via the project-level Mix compiler.

The underlying :ets table itself is unchanged -- this module just inserts a sync point before delegating. Your existing tables are fully usable.

Coverage

We wrap the operations most likely to participate in races:

• new/2, delete/1, delete_all_objects/1
• insert/2, insert_new/2
• lookup/2, lookup_element/3, lookup_element/4
• member/2
• delete/2, match_delete/2
• update_counter/3, update_counter/4, update_element/3
• select/2, match/2, match_object/2
• tab2list/1, info/1, info/2
• first/1, last/1, next/2, prev/2

Operations not in this list (e.g., :ets.give_away/3) are still callable as :ets.give_away(...) directly -- they just don't yield to the controller. File an issue if you need one wrapped.