8000 docs/reference: Update constrained docs now that tuples are const. · micropython/micropython@07e743e · GitHub
[go: up one dir, main page]

Skip to content

Commit 07e743e

Browse files
committed
docs/reference: Update constrained docs now that tuples are const.
Signed-off-by: Damien George <damien@micropython.org>
1 parent 2a7c9d4 commit 07e743e

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

docs/reference/constrained.rst

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -146,17 +146,12 @@ As in the string example, at runtime a reference to the arbitrarily large
146146
integer is assigned to the variable ``bar``. That reference occupies a
147147
single machine word.
148148

149-
It might be expected that tuples of integers could be employed for the purpose
150-
of storing constant data with minimal RAM use. With the current compiler this
151-
is ineffective (the code works, but RAM is not saved).
149+
Tuples of constant objects are also constant. For example:
152150

153151
.. code::
154152
155153
foo = (1, 2, 3, 4, 5, 6, 100000)
156154
157-
At runtime the tuple will be located in RAM. This may be subject to future
158-
improvement.
159-
160155
**Needless object creation**
161156

162157
There are a number of situations where objects may unwittingly be created and

0 commit comments

Comments
 (0)
0