Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Fix of #50 - volatile #53
Volatile checking needs to take all intersections into account; previously these
Plus several refactorings and additions.
Todo: We should find a better name for isVolatile. Maybe define the negation instead under the name
The example is in #50 is still accepted because isVolatile is not supposed to flag this one. is Volatile is an overapproximation of: The type is feasible now but it might become unfeasible by refining some of its abstract components. Feasibility of types has to be tested elsewhere. The right thing to do is to design and write a phase (what sued to be refChecks) that does this.