mirror of
https://github.com/ton-blockchain/ton
synced 2025-03-09 15:40:10 +00:00
f3e620f48c
This commit introduces nullable types `T?` that are distinct from non-nullable `T`. Example: `int?` (int or null) and `int` are different now. Previously, `null` could be assigned to any primitive type. Now, it can be assigned only to `T?`. A non-null assertion operator `!` was also introduced, similar to `!` in TypeScript and `!!` in Kotlin. If `int?` still occupies 1 stack slot, `(int,int)?` and other nullable tensors occupy N+1 slots, the last for "null precedence". `v == null` actually compares that slot. Assigning `(int,int)` to `(int,int)?` implicitly creates a null presence slot. Assigning `null` to `(int,int)?` widens this null value to 3 slots. This is called "type transitioning". All stdlib functions prototypes have been updated to reflect whether they return/accept a nullable or a strict value. This commit also contains refactoring from `const FunctionData*` to `FunctionPtr` and similar.
28 lines
568 B
Text
28 lines
568 B
Text
global op: (int, int) -> int;
|
|
|
|
fun check_assoc(a: int, b: int, c: int): bool {
|
|
return op(op(a, b), c) == op(a, op(b, c));
|
|
}
|
|
|
|
fun unnamed_args(_: int, _: slice, _: int) {
|
|
return true;
|
|
}
|
|
|
|
fun main(x: int, y: int, z: int): bool? {
|
|
op = `_+_`;
|
|
if (0) { return null; }
|
|
return check_assoc(x, y, z);
|
|
}
|
|
|
|
@method_id(101)
|
|
fun test101(x: int, z: int) {
|
|
return unnamed_args(x, "asdf", z);
|
|
}
|
|
|
|
/**
|
|
method_id | in | out
|
|
@testcase | 0 | 2 3 9 | -1
|
|
@testcase | 0 | 11 22 44 | -1
|
|
@testcase | 0 | -1 -10 -20 | -1
|
|
@testcase | 101 | 1 10 | -1
|
|
*/
|