MPS-10657 - Inline Variable checks whether the current node is in an for lValue position of an assignment or has an unary operation applied to it
MPS-18878 - Added constraints to only allow variable references as expressions inside Prefix and PostfiwXXXExpressions
MPS-18879 - Added Dataflow definition for Postfix and Prefix Increment/Decrement Expressions to correctly indicate the variable gets written to
Added the missing constraints and dataflow generated sources
MPS-18881 - excluded unary number operations as well as OperationAssignmentExpressions from the nodes to refactor by inline variable
MPS-10657 - polished the code a bit
MPS-18880 - Handled the two cases when the value has been assigned in either a unary number operation or an operation assignment expression
MPS-18878 - using isLValue() to detect allowed children for unary number expressions in checking rules
Rebuilt
Merge remote-tracking branch 'origin/master' into 3.1/vaclavInlineVariable
Merge remote-tracking branch 'origin/master' into 3.1/vaclavInlineVariable
Merge remote-tracking branch 'origin/master' into 3.1/vaclavInlineVariable
Merge remote-tracking branch 'origin/master' into 3.1/vaclavInlineVariable
MPS-18892 - ensured the statement containing the var reference that is being inlined is excluded from the list of applicable assignments
MPS-18892 - Assigments referring to the inlined variable from their right side should not be inlined, since the resulting code will have different semantics than the original
Rebuilt