Nicolas Cannasse

Was on Win 10 / VS Code 1.13.1 / Slighly old haxe (6/23 build)

Would this be solved by #217 ?

Ah right, I always forget that tasks are completely separate from completion :'( That's really meh, and looks like vscode is not planning any fix for it. I think that...

Yes, `"editor.suggestSelection": "first"` fixes it, thanks and yes I think this should be in README so leaving it open.

The diagnostics don't also get removed when compiling until you switch to the file again. So if in A.hx you have an error related to B.hx, and you modify B.hx...

Wow, that seems very problematic that errors keep showing even after they have been dealt with. But I'm not sure I understand : the compiler can actually add "problems", is...

One additional option would be to redo diagnostics for all files having reported problems each time you change one other file

I correct then: having reported "errors" (no warnings)

I have a different approach: to me, it is fine if you eventually miss some diagnostics - if the file has never been opened for instance, or in other cases...

Looks like the tasks limitations are overwhelming. Any way to avoid them entirely and have our own way to run compilation by using haxe settings + setting a shortcut on...