Gestartet durch entfernten Rechner 192.30.252.34192.30.252.3497641868a95435ade010cb4e27067fc5d4ae272d25941868a95435ade010cb4e27067fc5d4ae272d259refs/remotes/origin/master41868a95435ade010cb4e27067fc5d4ae272d25941868a95435ade010cb4e27067fc5d4ae272d259refs/remotes/origin/master41868a95435ade010cb4e27067fc5d4ae272d25941868a95435ade010cb4e27067fc5d4ae272d259refs/remotes/origin/masterhttps://github.com/wurstscript/WurstScript.git90715testReportfalse#9761558463737407Wurst #976976falsefalse9764758FAILURE1538424939998https://grill.wurstlang.org/hudson/user/frotty/my-views/view/all/job/Wurst/976/de.peeeq.wurstscript/src/test/java/tests/wurstscript/tests/FlowAnalysisTests.javade.peeeq.wurstscript/src/main/java/de/peeeq/wurstscript/validation/controlflow/DataflowAnomalyAnalysis.java41868a95435ade010cb4e27067fc5d4ae272d2591538424741000https://grill.wurstlang.org/hudson/user/peter.peqPeter.peqPeter.peq@googlemail.comnew compilation error when trying to access destroyed var as suggested by Frotty in #731 when a local variable or 'this' has been destroyed this is stored in the control flow analysis and subsequent uses of the variable become an error. Note that this is not a complete analysis, it will not detect aliasing problems and does not do inter-procedure analysis, for example: let a = new A() let b = a destroy b a.doSomething() // just a runtime error 2018-10-01 22:12:21 +020041868a95435ade010cb4e27067fc5d4ae272d259new compilation error when trying to access destroyed vareditde.peeeq.wurstscript/src/main/java/de/peeeq/wurstscript/validation/controlflow/DataflowAnomalyAnalysis.javaeditde.peeeq.wurstscript/src/test/java/tests/wurstscript/tests/FlowAnalysisTests.javagithttps://grill.wurstlang.org/hudson/user/peter.peqPeter.peq