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
Issues #16237 and #16238 propose convenience features for implicitly reading atomics and supporting special operators on them that map to their methods. This issue asks whether we should support things like + on two atomics or + reduce on an array of atomics. It may be that these will just fall out if we adopt #16237, or they may require extra work. Would such support round out our atomic story or be a bridge too far?
The text was updated successfully, but these errors were encountered:
I think this will fall out from #16237 and #16238. I'm in favor of both of those, but even if we don't end up implementing them, I'd be in favor of supporting this since it seems like a common case. The main argument against supporting operator overloads for atomics is wanting it to be very visible that atomic operations are happening, but I don't think that applies in the reduction case.
I would add my voice to those of @ronawho and @gbtitus in what you are suggesting for both this and the two other related issues, All of these issues did remind me to look at which is doing Rust on this topic.
Issues #16237 and #16238 propose convenience features for implicitly reading atomics and supporting special operators on them that map to their methods. This issue asks whether we should support things like
+
on two atomics or+ reduce
on an array of atomics. It may be that these will just fall out if we adopt #16237, or they may require extra work. Would such support round out our atomic story or be a bridge too far?The text was updated successfully, but these errors were encountered: