From: sawadatsuyoshi@... Date: 2016-08-03T13:58:41+00:00 Subject: [ruby-core:76681] [Ruby trunk Bug#12607] Ruby needs an atomic integer Issue #12607 has been updated by Tsuyoshi Sawada. Sorry, I do not clearly understand why the original Integer class cannot be made atomic. If it is not possible or if there would be any problem, can someone explain why that is? Ideally, I think it would be better if the original Integer class can be modified in some way rather than introducing additional classes. ---------------------------------------- Bug #12607: Ruby needs an atomic integer https://bugs.ruby-lang.org/issues/12607#change-59899 * Author: Shyouhei Urabe * Status: Open * Priority: Normal * Assignee: * ruby -v: * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- (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: