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
Copy file name to clipboardExpand all lines: sips/pending/_posts/2013-05-31-improved-lazy-val-initialization.md
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -654,6 +654,7 @@ We expect that the proposed changes will not change the memory footprint for mos
654
654
Since we now use 2 bits per lazy val field instead of 1, for classes having 4 or less lazy val field declarations the memory footprint per instance will thus not grow. For classes having more lazy val field declarations the memory footprint per instance will in most cases not grow since the objects have to be aligned to an 8 byte boundary anyway.
655
655
656
656
We measured the memory footprint of an array of objects with single lazy val fields. The memory footprint did not change with respect to the current version \[[6][6]\]\[[7][7]\].
657
+
The detailed experimental measurements graphs of memory footprint can be seen in graphs.\[[18][18]\]
657
658
658
659
### Performance ###
659
660
@@ -700,7 +701,7 @@ We would like to thank Peter Levart and the other members of the concurrency-int
700
701
4.[Program Hangs If Thread Is Created In Static Initializer Block][4]
701
702
5.[Java Language Specification, 12.4.2][5]
702
703
6.[GitHub Repo with Microbenchmarks][6]
703
-
7.[Evaluation Results][7]
704
+
7.[Performance Evaluation Results][7]
704
705
8.[ScalaMeter GitHub Repo][8]
705
706
9.[Lazy Vals in Dotty, Scala Internals Mailing list, February 2014][9]
706
707
10.[Lazy Vals in Dotty, Dotty Internals Mailing list, February 2014][10]
@@ -711,14 +712,15 @@ We would like to thank Peter Levart and the other members of the concurrency-int
711
712
15.[Introducing Scalafix: a migration tool for Scalac to Dotty, October 2016][15]
0 commit comments