pri2ir: dynamic unary & binary expressions
NB1 Not every dynamic unary or binary expression is translated to dynamic operator expressions literally. For example, assignments and increments can have safe calls in LHS, which require some extra logic. NB2 There are some open design questions left regarding how dynamic expressions should actually be translated.
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
FILE fqName:<root> fileName:/dynamicUnaryOperator.kt
|
||||
FUN name:testUnaryMinus visibility:public modality:FINAL <> (d:dynamic) returnType:dynamic flags:
|
||||
VALUE_PARAMETER name:d index:0 type:dynamic flags:
|
||||
BLOCK_BODY
|
||||
RETURN type=kotlin.Nothing from='testUnaryMinus(dynamic): dynamic'
|
||||
DYN_OP operator=UNARY_MINUS type=dynamic
|
||||
receiver: GET_VAR 'value-parameter d: dynamic' type=dynamic origin=null
|
||||
FUN name:testUnaryPlus visibility:public modality:FINAL <> (d:dynamic) returnType:dynamic flags:
|
||||
VALUE_PARAMETER name:d index:0 type:dynamic flags:
|
||||
BLOCK_BODY
|
||||
RETURN type=kotlin.Nothing from='testUnaryPlus(dynamic): dynamic'
|
||||
DYN_OP operator=UNARY_PLUS type=dynamic
|
||||
receiver: GET_VAR 'value-parameter d: dynamic' type=dynamic origin=null
|
||||
FUN name:testExcl visibility:public modality:FINAL <> (d:dynamic) returnType:dynamic flags:
|
||||
VALUE_PARAMETER name:d index:0 type:dynamic flags:
|
||||
BLOCK_BODY
|
||||
RETURN type=kotlin.Nothing from='testExcl(dynamic): dynamic'
|
||||
DYN_OP operator=EXCL type=dynamic
|
||||
receiver: GET_VAR 'value-parameter d: dynamic' type=dynamic origin=null
|
||||
Reference in New Issue
Block a user