DatenMetzgerX / ESChecker

97%

master: 96%

LAST BUILD ON BRANCH type-inference-call-expression

branch: type-inference-call-expression

CHANGE BRANCH

x

Reset

• type-inference-call-expression
• PA1-Final
• add-node-5-to-build
• array-type
• arrow-expressions
• cleaneups
• data-flow-analysis
• do-while-statement
• feedback-luc
• finalisierung-report
• fix-function-call-in-loop
• fix-this-inside-object-methods
• for-of-statement
• function-declaration-hoisting
• ignore-empty-statements-in-cfg
• improve-documentation
• invocation-of-any-type-values
• master
• more-sophisticated-recursion-detection
• npm-package
• outline
• rename-specs-to-spec
• shrinkwrap-dependencies
• string-built-in-methods
• support-arrow-functions-with-expression-body
• throw-statement
• type-inference-cleanups
• type-inference-for-statement
• type-inference-if-statements
• type-inference-record
• v0.0.2
• v0.0.3
• v0.0.4
• v0.0.5

Build # 151

Build Type

push

travis-ci

Committed by DatenMetzgerX

Commit Message

Implement inlining of function calls

Function calls are inlined to perform type inference in the context of the
caller.

The commit also contains the change that equals does not need to be true
even if the types have the same id. The reason for this is, that
a modified type is never equal to the other with the same id. The equals
funciton is used to calculate the difference of two type environments and
if types with the same id are equal, then changes to these are not
shown as differences.

Modification to a record type (like adding or changing properties)
returns now a record type that has the same id as the original one.
This is needed to be able to detect if an argument type in a function
call has changed or not. If the id would change, then there is no way
to detect if the type has been modified (e.g. adding properties) or a
complete new type has been assigned.

fixes #34

Run Details

1152 of 1189 relevant lines covered (96.89%)

144.3 hits per line