From: chris@... Date: 2021-01-13T23:45:48+00:00 Subject: [ruby-core:102076] [Ruby master Feature#12607] Ruby needs an atomic integer Issue #12607 has been updated by chrisseaton (Chris Seaton). > You can achieve something similar with Object.new.object_id You may want them to be consecutive. > Why atomic though... This can all be achieved with a Ractor. A Ractor send has relatively high synchronisation overhead - an atomic integer is conventionally implemented at the cache-coherence level and is lock-free. I can only offer that I use atomic integers for many things fairly frequently in my working life. ---------------------------------------- Feature #12607: Ruby needs an atomic integer https://bugs.ruby-lang.org/issues/12607#change-89936 * Author: shyouhei (Shyouhei Urabe) * Status: Feedback * Priority: Normal * Assignee: ko1 (Koichi Sasada) ---------------------------------------- (This one was derived from bug #12463) Although I don't think += would become atomic, at the same time I understand Rodrigo's needs of _easier_ counter variable that resists inter-thread tampering. I don't think ruby's Integer class can be used for that purpose for reasons (mainly because it is not designed with threads in mind). Rather we should introduce a integer class which is carefully designed. Why not import Concurrent::AtomicFixnum into core? -- https://bugs.ruby-lang.org/ Unsubscribe: