From 8343dd8f814e076411fc1a5b79558fe06b200fd9 Mon Sep 17 00:00:00 2001 From: Clay-Mysten <100217682+Clay-Mysten@users.noreply.github.com> Date: Fri, 19 Aug 2022 08:39:29 -0700 Subject: [PATCH] Update doc/src/build/move/sui-move-library.md Co-authored-by: Sam Blackshear --- doc/src/build/move/sui-move-library.md | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/src/build/move/sui-move-library.md b/doc/src/build/move/sui-move-library.md index 75df458f036e0..9c51ed3d9eecb 100644 --- a/doc/src/build/move/sui-move-library.md +++ b/doc/src/build/move/sui-move-library.md @@ -77,7 +77,6 @@ transfer::share_object(obj); ``` After this call, `obj` stays mutable, but becomes shared by everyone, i.e. anyone can send a transaction to mutate this object. However, such an object cannot be transferred or embedded in another object as a field. For more detail, see the [shared objects](../../learn/build/objects.md#shared) documentation. -Shared mutable objects can be powerful in that they make programming a lot simpler in many cases. However, shared objects are also more expensive to use: they require a full sequencer (a.k.a. a [consensus engine](../../learn/architecture/consensus.md) to order the transactions that touch the shared object, which means longer latency/lower throughput and higher gas cost. One can see the difference in the two programming schemes by looking at the two implementations of TicTacToe: [No Shared Object](https://github.com/MystenLabs/sui/blob/main/sui_programmability/examples/games/sources/tic_tac_toe.move) vs. [Shared Object](https://github.com/MystenLabs/sui/blob/main/sui_programmability/examples/games/sources/shared_tic_tac_toe.move). ## Transaction context `TxContext` module provides a few important APIs that operate based on the current transaction context.