From 3ce5945cbe8d169f5ec17a2b731521c0284de553 Mon Sep 17 00:00:00 2001 From: Alex Hansen Date: Thu, 16 Jun 2022 13:41:17 -0700 Subject: [PATCH] remove WIP note on storage attributes (#2016) --- docs/src/blockchain-development/purity.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/src/blockchain-development/purity.md b/docs/src/blockchain-development/purity.md index 024df06fc4a..26612c76823 100644 --- a/docs/src/blockchain-development/purity.md +++ b/docs/src/blockchain-development/purity.md @@ -1,7 +1,5 @@ # Purity -**_The attributes `#[storage(read)]` and `#[storage(read, write]` introduced below are still in active development. There is no need to apply them at the moment._** - A function is _pure_ if it does not access any [persistent storage](./storage.md). Conversely, the function is _impure_ if it does access any storage. Naturally, as storage is only available in smart contracts, impure functions cannot be used in predicates, scripts, or libraries. A pure function cannot call an impure function. In Sway, functions are pure by default but can be opted into impurity via the `storage` function attribute. The `storage` attribute may take `read` and/or `write` arguments indicating which type of access the function requires.