Variabel Status dan Tata Letak Penyimpanan
Pahami perbedaan antara storage, memory, dan calldata, serta cara variabel status bertahan di blockchain.
Variabel Status dan Tata Letak Penyimpanan adalah pelajaran Blockchain Smart Contracts with Solidity gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Blockchain Smart Contracts with Solidity, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Blockchain Smart Contracts with Solidity mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
What are State Variables?
Welcome to understanding how data lives on the blockchain! In Solidity, state variables are special variables whose values are permanently stored in the contract's storage on the blockchain.
Think of them as the persistent memory of your smart contract. Their values are saved even after a function finishes executing and across different transactions.
Data Locations in Solidity
Solidity uses different data locations to manage where information is stored during contract execution. These locations have big impacts on gas costs and how your variables behave.
storage: Permanent state on the blockchain.memory: Temporary data for function execution.calldata: Read-only data for external function arguments.
Deep Dive into `storage`
Variables declared at the contract level (outside of any function) are automatically assigned to storage. These are your contract's state variables.
Data in storage is expensive to modify because every change is written to the blockchain, making it permanent and immutable (in the sense of its history).
`storage` in Action
This contract stores a number in a state variable. Notice how myNumber keeps its value between calls to setNumber and getNumber.
pragma solidity ^0.8.0;
contract StorageExample {
uint public myNumber; // This is a state variable, lives in storage
function setNumber(uint _num) public {
myNumber = _num;
}
function getNumber() public view returns (uint) {
return myNumber;
}
}Understanding `memory`
memory is a temporary data location. It's used for variables that exist only during a function call and are discarded once the function execution completes.
It's cheaper than storage for temporary data, making it ideal for arrays, strings, or structs that are created and used within a single function.
`memory` in Action
This function creates a string in memory, modifies it, and returns it. The string only exists for the duration of the function call.
pragma solidity ^0.8.0;
contract MemoryExample {
function greet(string memory _name) public pure returns (string memory) {
string memory greeting = "Hello, ";
// Use abi.encodePacked for simple string concatenation
return string(abi.encodePacked(greeting, _name, "!"));
}
}Introducing `calldata`
calldata is a special read-only data location used exclusively for external function parameters. It's even cheaper than memory because data is not copied into memory, just referenced.
You cannot modify calldata. It's typically used for large data passed to external functions, saving gas by avoiding copies.
`calldata` in Action
This external function takes a string as calldata. Notice it's read-only and efficient for external calls.
pragma solidity ^0.8.0;
contract CalldataExample {
// This function can only be called externally
function processData(bytes calldata _data) external pure returns (uint) {
// You cannot modify _data directly, but can read its properties
return _data.length; // Returns the byte length of the data
}
// Another example returning calldata directly
function echoString(string calldata _message) external pure returns (string calldata) {
return _message;
}
}Comparing Data Locations
Choosing the right data location is crucial for gas optimization and correct contract behavior:
- Storage: Permanent, expensive, contract state.
- Memory: Temporary, cheaper, within-function variables.
- Calldata: Read-only, cheapest, external function arguments.
Always use the most restrictive and cheapest option possible.
How Storage is Organized
Solidity packs state variables into 256-bit (32-byte) storage slots to save space and gas. Smaller types (like uint8, bool) can be packed together into a single slot.
However, this packing can be complex and depends on the order of variable declarations. Understanding it helps optimize gas costs, especially with structs and arrays.
Data Location Quiz
Which data location is used for permanent storage of a contract's state variables on the blockchain?
Summary of Data Locations
Great job! You've learned about the fundamental data locations in Solidity: storage, memory, and calldata.
- State variables live in
storage, making them persistent. memoryis for temporary data during function execution.calldatais for efficient, read-only external function arguments.
Understanding these helps you write more efficient and correct smart contracts. Next, we'll explore complex data structures like Mappings and Dynamic Arrays!
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Variabel Status dan Tata Letak Penyimpanan” gratis?
Ya — teks lengkap “Variabel Status dan Tata Letak Penyimpanan” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Blockchain Smart Contracts with Solidity, upgrade ke CoddyKit PRO. Kursus Blockchain Smart Contracts with Solidity mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Variabel Status dan Tata Letak Penyimpanan”?
Pahami perbedaan antara storage, memory, dan calldata, serta cara variabel status bertahan di blockchain. Kamu berlatih Blockchain Smart Contracts with Solidity dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Blockchain Smart Contracts with Solidity?
Tidak diperlukan pengalaman sebelumnya. Blockchain Smart Contracts with Solidity di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.
Berapa lama pelajaran “Variabel Status dan Tata Letak Penyimpanan” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Blockchain Smart Contracts with Solidity ini?
Ya. Setiap pelajaran Blockchain Smart Contracts with Solidity menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Variabel Status dan Tata Letak Penyimpanan
- Mapping dan Larik Dinamis
- Peristiwa dan Data Logging
- Slot Penyimpanan dan Optimasi Gas