can parse private names (#1)

do a really rough, quick-and-dirty unblock-people job of letting #foo be parse-able.

steps to test:

npm run lint && npm test
See https://bbgithub.dev.bloomberg.com/javascript-guild/typescript-private-fields/ quick start guide for seeing the AST
CI testing coming soon

Author: Maxwell Heiber

src/compiler/scanner.ts

@@ -1725,10 +1725,7 @@ namespace ts {
                         return token = SyntaxKind.Unknown;
                     case CharacterCodes.hash:
                         pos++;
-                        if (
-                            languageVersion === ScriptTarget.ESNext
-                            && isIdentifierStart(ch = text.charCodeAt(pos), languageVersion)
-                        ) {
+                        if (isIdentifierStart(ch = text.charCodeAt(pos), languageVersion)) {
                             tokenFlags |= TokenFlags.PrivateName;
                             pos++;
                             while (pos < end && isIdentifierPart(ch = text.charCodeAt(pos), languageVersion)) pos++;
@@ -1739,7 +1736,11 @@ namespace ts {
                             return token = SyntaxKind.Identifier;
                         }
                         error(Diagnostics.Invalid_character);
+<<<<<<< HEAD
                         // no `pos++` because already advanced at beginning of this `case` statement
+=======
+                        pos++;
+>>>>>>> can parse private names (#1)
                         return token = SyntaxKind.Unknown;
                     default:
                         if (isIdentifierStart(ch, languageVersion)) {