Date: Sun, 28 May 2023 14:32:15 -0400
On 5/28/23 14:11, Federico Kircheis wrote:
>
> You might have missed what I and other wrote.
> (and in my experience you do not only loose time waiting and
> synchronizing threads, which depending on the environment are not
> nanoseconds, but also create a lot of code-bloat/gigantic binaries with
> this approach)
>
> You might have prevented data races, but you did not gain thread safety.
> On the contrary, thread issues are more difficult to reproduce and
> diagnose.
Sorry I just skimmed the link without understanding it but your solution
would apply to all variable instantiations: from elements, to
containers, to top level classes.
Your approach is a great solution indeed. Under what license are your
headers subject to?
>
> You might have missed what I and other wrote.
> (and in my experience you do not only loose time waiting and
> synchronizing threads, which depending on the environment are not
> nanoseconds, but also create a lot of code-bloat/gigantic binaries with
> this approach)
>
> You might have prevented data races, but you did not gain thread safety.
> On the contrary, thread issues are more difficult to reproduce and
> diagnose.
Sorry I just skimmed the link without understanding it but your solution
would apply to all variable instantiations: from elements, to
containers, to top level classes.
Your approach is a great solution indeed. Under what license are your
headers subject to?
-- Logo <https://www.fornux.com/> *Phil Bouchard* facebook icon <https://www.linkedin.com/in/phil-bouchard-5723a910/> Founder & CEO T: (819) 328-4743 E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com> 8 rue de la Baie| Gatineau (Qc), J8T 3H3 Canada Banner <https://goglobalawards.org/> Le message ci-dessus, ainsi que les documents l'accompagnant, sont destinés uniquement aux personnes identifiées et peuvent contenir des informations privilégiées, confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce message par erreur, veuillez le détruire. This communication (and/or the attachments) is intended for named recipients only and may contain privileged or confidential information which is not to be disclosed. If you received this communication by mistake please destroy all copies.
Received on 2023-05-28 18:32:16