Jump to content

Double-checked locking: Revision history


For any version listed below, click on its date to view it. For more help, see Help:Page history and Help:Edit summary. (cur) = difference from current version, (prev) = difference from preceding version, m = minor edit, → = section edit, ← = automatic edit summary

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)

30 October 2023

7 September 2023

5 August 2023

21 May 2023

26 March 2023

16 March 2023

26 January 2023

30 December 2022

24 October 2022

  • curprev 15:5715:57, 24 October 2022216.154.2.79 talk 18,938 bytes +49 Clarified when double checked locking is suitable. It all involves the need for a fence. The example with Java 1.4 is a bit of a red herring, as doesn't have a coherent memory model (as the next paragraph indicated) nor is in use. undo Tag: Visual edit

27 May 2022

19 May 2022

17 May 2021

8 May 2021

2 April 2021

21 February 2021

13 January 2021

18 December 2020

27 November 2020

22 October 2020

28 August 2020

6 August 2020

14 July 2020

5 May 2020

17 April 2020

7 February 2020

  • curprev 04:2304:23, 7 February 2020Funny falcon talk contribs 18,976 bytes +114 →‎Usage in Golang: Go's slice is a struct of three fields. It is incorrect to compare it directly and then use without synchronization in concurrent environment. For example, code in a line which sets arr could already set length, but didn't aet pointer. Then slice will not be nil, and comparison will succeed. But use of such half-initialized slice will lead to swgmentaion fault undo Tags: Mobile edit Mobile web edit

30 November 2019

23 November 2019

4 July 2019

2 July 2019

4 June 2019

30 May 2019

18 February 2019

8 January 2019

22 October 2018

29 July 2018

28 July 2018

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)