From: daniel@...42.com Date: 2021-01-14T03:41:05+00:00 Subject: [ruby-core:102082] [Ruby master Feature#12607] Ruby needs an atomic integer Issue #12607 has been updated by Dan0042 (Daniel DeLorme). chrisseaton (Chris Seaton) wrote in #note-32: > An use-case I was working on earlier today was profiling operations like coverage and sampling tools. Ah yes, beautiful example! Accumulating metrics require both atomicity and performance. ---------------------------------------- Feature #12607: Ruby needs an atomic integer https://bugs.ruby-lang.org/issues/12607#change-89941 * 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: