There are two issues addressed here, meant to help support down-level emit for Async Functions (and optionally Generators) in ES5/3.

Currently, the objectAllocator for both compiler and services sets the default node pos/end to 0. While generally this seems a valid default, we always set the pos and end of every node created by the parser to a non-negative value when we call createNode and finishNode. Whenever we create a synthesized node in the emitter, we explicitly set the pos/end to -1. For the down-level rewrite, I will be generating many synthesized nodes and am looking to centralize node creation into a set of factory methods for creating each of our various types of nodes. I plan to have both parser and emitter rely on this to centralize node creation, and as such it seems reasonable to treat any new Node as synthesized by default (with a pos/end of -1) until such time as the parser explicitly sets the position.

In addition, the nodeIsMissing function currently tests whether the node exists, is not the EndOfFileToken, and that its pos and end are not the same value. This means that any any synthesized node would be considered "missing". As such, I have added a condition that the node's pos must be non-negative to be considered "missing".