This is intentionally not specific and not really actionable, but there are some changes to how storage will work in Sway that may have an impact on the approaches we took in the contracts. E.g. a StorageMap<K, StorageVec<V>> may be possible, in which case we should move away from StorageMapVec. Or in the merkle library, where we make storage accesses sort of "manually" by reading and writing to specific storage slots, we may be able to compose with higher lvl storage libraries
This is intentionally not specific and not really actionable, but there are some changes to how storage will work in Sway that may have an impact on the approaches we took in the contracts. E.g. a
StorageMap<K, StorageVec<V>>
may be possible, in which case we should move away from StorageMapVec. Or in the merkle library, where we make storage accesses sort of "manually" by reading and writing to specific storage slots, we may be able to compose with higher lvl storage librariesRelevant issue to keep an eye on: https://github.com/FuelLabs/sway/pull/4297