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: components/Starknet/modules/guides/pages/starknet-by-example/storage.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ mod Contract {
36
36
Both contracts above generate identical Sierra code. The compiler only generates code for storage variables that are actually used in contract functions. Declaring unused storage variables has no impact on contract size or gas costs.
37
37
====
38
38
39
-
For more complex data structures, see xref:starknet-by-example/storing_custom_types)[Storing Custom Types].
39
+
For more complex data structures, see xref:starknet-by-example/custom-types#storing_custom_types[Storing Custom Types].
40
40
41
41
### Storage Space (advanced)
42
42
@@ -76,4 +76,4 @@ In our previous contract example:
76
76
// [TIP]
77
77
// ====
78
78
// Notice how many bits are left unused in each slot? This can make storage operations expensive. To optimize storage usage, you can pack multiple variables together. Learn more in (/advanced-concepts/optimisations/store_using_packing)[Storage Optimisation].
0 commit comments