Hi @OrangeShark, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.

TTYL, MSBOT;

I noticed the extra, bogus baselines too. Just take them out of the PR for now while we figure out how they got there.

@sandersn Okay, I took them out and updated the pull request.

Looks good except for a minor comment change in the baseline.
Plus there is the mystery of the previously-missing error message for ...arg?. Maybe the parser change somehow fixed it in passing?

I changed the comment. I also believe the reason for the previously missing error message for ...arg? was because the error was from the checker while the previous error of having a parameter property for rest parameters was from the parser. Now that the error is discovered in the checker, it now shows other error messages from the checker.

For example compiling this

function a3(...b?) {}

class C {
    constructor(public ...temp) {}
}

only prints error TS1005: ',' expected. currently.

👍

@RyanCavanaugh or @DanielRosenwasser can you take a look at the wording of the new error messages? I want to get another pair of eyes besides mine.

This change makes me happy 💯. We're just waiting on the Travis Build before we merge right now.

Thanks again, @OrangeShark.