Remove a known issue about arrays being immutable (FuelLabs#3502)

Arrays can now be mutable.
cold-briu · Dec 3, 2022 · ec819e6 · ec819e6
1 parent a33e833
commit ec819e6
Showing 1 changed file with 0 additions and 2 deletions.
diff --git a/docs/src/reference/known_issues_and_workarounds.md b/docs/src/reference/known_issues_and_workarounds.md
@@ -8,8 +8,6 @@
 
 * [#1182](https://github.com/FuelLabs/sway/issues/1182) Arrays in a `storage` block are not yet supported. See the [Manual Storage Management](../blockchain-development/storage.md#manual-storage-management) section for details on how to use `store` and `get` from the standard library to manage storage slots directly. Note, however, that `StorageMap<K, V>` _does_ support arbitrary types for `K` and `V` without any limitations.
 
-* [#428](https://github.com/FuelLabs/sway/issues/428): Arrays are currently immutable which means that changing elements of an array once initialized is not yet possible.
-
 * [#1796](https://github.com/FuelLabs/sway/issues/2465): It is not yet allowed to use `StorageMap<K, V>` as a component of a complex type such as a struct or an enum.
 
 * [#2647](https://github.com/FuelLabs/sway/issues/2647): Currently, it is only possible to define configuration-time constants that have [primitive types](../basics/built_in_types.md#primitive-types) and that are initialized using literals.