Type information

Why use this example

Use this pattern to explore how Solidity represents typed values and how state-changing expressions affect storage. The entry isolates type information so its input, result, and state changes stay easy to compare.

Solidity to run

interface IPing { function ping() external; }
contract Probe { function answer() external pure returns (uint256) { return 42; } }
function inspectTypes() public pure returns (int8, uint16, bytes4, uint256, uint256) {
  return (type(int8).min, type(uint16).max, type(IPing).interfaceId, type(Probe).creationCode.length, type(Probe).runtimeCode.length);
}

inspectTypes()

Official Solidity reference

Compare this focused investigation with the complete language definition in the Solidity documentation.

What to expect

The transcript shows signed and unsigned integer limits, the interface ID, and the creation and runtime bytecode lengths.

Continue the investigation

Change a value, add another expression, or open Inspect after the run. Accepted entries remain available to the next entry, and the clean replay keeps the complete result reproducible.