Fix crash in signature conformance checking
Update field name in syntax tree.
Fixing code after pull.
When contextually instantiating signatures, use the actual (potentially instantiated) signature parameter types, as opposed to the parameter types linked to the AST nodes (which may not themselves be instantiated).
Remove code that had inner types being instantiated to 'any' during type inference.  It wasn't spec conformant, and could lead to invalid caching of instantiations.
(The latter could result in heisenbugs.)
Move more of the argument inferencing logic into the ArgumentContext object
Account for recent renamings and update baselines
fix getTypeParameterSignatureAtPosition to not error with unexpected ast
Fix the overload signature assignability check for generic overload with rest parameters
Merge branch 'develop' of https://git01.codeplex.com/typescript into develop
Add test case
Test case for generic interface implementation issue.
Improve parser error recovery.

Jake ran into a repro from the F12 team where we ended up producing a pretty ugly parse tree
when we encountered certain constructs in an unterminated block.  Specifically, if something
like "interface Foo" was encountered we wouldn't properly bail out and parse that as an
interface.  This was due to the parsing askign the question "is this an expression" and
thinking "yes" due to 'interface' being a javascript identifier rather than a keyword.  We
need to be a bit less lenient here so that we can produce a more sensible tree for the rest
of the system to use.

Jake will be addressing hte crash that happens later in the system because of code that
wasn't expecting such a bizarre looking tree.
When we asynchrously get the text tooltip for a completion entry item, we need to ensure that the decl we've cached is resolved first.
Update test.
Fix the declaration emit for the enum elements
The enum members with implicitly numbered values would have their constant emitted into the .d.ts