docs: add sway memory model

[matt-user]

Description

Developers get confused by Sway's memory model as it is different from Rust's. So I added this to the docs.

closes https://app.asana.com/0/1207924201336629/1208429018056446

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• x ] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[sdankel]

lgtm

[Bnymn1306]

Snapshot has been taken 13 Ara 2024 Cum 16:13 tarihinde Matt ***@***.***> şunu yazdı:

…

***@***.**** commented on this pull request. ------------------------------ In docs/book/src/reference/rust_differences.md <#6775 (comment)>: > @@ -34,3 +34,9 @@ struct MyStruct { field_two: bool, } ``` + +## Memory Allocation + +In Rust, the borrow checker implements Rust's [ownership system](https://doc.rust-lang.org/1.8.0/book/ownership.html) + +In Sway, there is no borrow checker. This means there is no concept of ownership, borrowing, or lifetimes. Instead, objects are copied and moved similar to C++. Also Sway does not have any destructors nor `Drop` traits. This means allocated memory lives for the entire transaction and is not deallocated until the end of the transaction. A transaction can contain 65 MB of memory. I couldn't find it in the specs, but I linked to where it is in our code — Reply to this email directly, view it on GitHub <#6775 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATO66TZ37AEWLZLRM3MGLOT2FLMNXAVCNFSM6AAAAABTC6GS5WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKMBSGI3DSMRVG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>