You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After spending some time, I realized, that the is no a word about concurrent write of user data, only the registry itself. So, the developer should to manage it. This means, that for my case I should create a subclass, which allows the concurrent immutable access to the data.
Will do it anyway for my needs. Is it good idea to add it as a PR to -edge afterwards?
What is your use-case?
Yeah keep the new class next to the lazy_reqister in edge for now please. I would recommend to submit a draft PR so we can discuss early. Thanks!
pitr-ch
added
enhancement
Adding features, adding tests, improving documentation.
and removed
bug
A bug in the library or documentation.
labels
Aug 25, 2019
If yout take a look at
concurrent-ruby/lib-edge/concurrent/lazy_register.rb
Line 61 in bbeacbc
When block evaluation time is stochastic, then even 2
register
calls will produce unpredictable result.Will be happy to fix it, if u don't mind.
The text was updated successfully, but these errors were encountered: