From 2dd0c8008ef0f66fea0fe69aa2063ef5ceed4f31 Mon Sep 17 00:00:00 2001 From: 0xf90c Date: Fri, 21 Jun 2024 11:05:26 -0700 Subject: [PATCH] update --- rustbook-uz/src/ch15-05-interior-mutability.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/rustbook-uz/src/ch15-05-interior-mutability.md b/rustbook-uz/src/ch15-05-interior-mutability.md index 5954bc2..3b1794b 100644 --- a/rustbook-uz/src/ch15-05-interior-mutability.md +++ b/rustbook-uz/src/ch15-05-interior-mutability.md @@ -21,6 +21,8 @@ runtime performance because all the analysis is completed beforehand. For those reasons, checking the borrowing rules at compile time is the best choice in the majority of cases, which is why this is Rust’s default. +Borrowing qoidalarini kompilyatsiay vaqtida tekshirishning yaxshi tarafi xatolarni development vaqtida tezroq topishdir, va runtime unumdorligiga ta'sir ko'rsatmaydi chunki hamma analizlar oldindan qilingan bo'ladi. Ko'p hollarda borrowing qoidalarini kompilyatsiya vaqtida tekshirish eng yaxshi tanlovdir, sababi ushbu xususiyat Rustda odatiy xususiyatidir. + The advantage of checking the borrowing rules at runtime instead is that certain memory-safe scenarios are then allowed, where they would’ve been disallowed by the compile-time checks. Static analysis, like the Rust compiler,