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.
13 lines
334 B
Text
13 lines
334 B
Text
fun acceptMutateNullableTensor(mutate self: (int, int)?) {
|
|
}
|
|
|
|
fun cantModifyTupleIndexWithTypeTransition() {
|
|
var t = [1, null];
|
|
t.1.acceptMutateNullableTensor();
|
|
}
|
|
|
|
/**
|
|
@compilation_should_fail
|
|
@stderr can not call method for mutate `(int, int)?` with object of type `null`
|
|
@stderr because mutation is not type compatible
|
|
*/
|