Give a semantic error on with statements
Type check the expression of the 'with' statement
Allow reserved words in type queries.
Fixes #181.
Improved lookahead for arrow functions.

Fixes issue #34.

Specifically:
    * We no longer automatically assume "()" is a function expression. It must be followed by an arrow, colon, or curly brace.
    * If an arrow is missing following a signature, but a curly brace is present, we assume the user forgot the arrow and try to parse the body anyway.
Delete some baselines so we can rename them with different casing for Linux
Renames of existing baselines with casing to match the test files
Trying to fix newlines in sourcemap baselines for *nix
Make a test that explicitly sets newline type
Be less clever, just use \r\n for newlines by default, tests can opt into different newlines, fix one more file casing test
Addressing CR feedback.
Making allowReservedWords parameter of parseEntityName non-optional.
do not propagate property name as name for function expression
Covered more cases for arrow functions omitting arrows.

Specifically where we have a full signature followed by an open curly brace.
Merge branch 'master' into errorOnWithStatement
Merge branch 'master' into errorOnWithStatement
Merge pull request #176 from Microsoft/errorOnWithStatement

Give a semantic error on with statements
Track control flow contexts in the parser, and give errors for break, continue, return
Add errors for break and continue statements
Improved "certainty" when parsing arrow-function-lookin' expressions.
Remove inModuleBody
enabled strict mode