Closed wolfgang42 closed 5 years ago
This bug seems to occur only for 3.4.0-dev.20190313
and after, I have tried one by one from 3.4.0-dev.20190329
backwards until that.
[here is a more simple reproducible code](https://www.typescriptlang.org/play/index.html#src=function%20x(a%2C%20b%2C%20c)%20%7B%0D%0A%20%20%20%20return%20%60%24%7Ba%7D%3A%24%7Bb%7D%3A%24%7Bc%7D%60%3B%0D%0A%7D%0D%0A%0D%0Afunction%20y()%20%7B%0D%0A%20%20%20%20return%20x('a'%2C%20...arguments)%3B%0D%0A%7D)
You will see NO compiled output since it crashed. Open the browser console to view the Debug Failure. False expression.
error.
@RyanCavanaugh would you consider doing a bugfix release for 3.4.x with #30758 in it instead of waiting for TypeScript 3.5? Just tried to upgrade our codebase to TS 3.4 and was blocked by this issue today.
@RyanCavanaugh Also looking for a response here. This seems to be a bug introduced in 3.4
so it would make sense to patch it before 3.5
. This is also blocking the upgrade for a few projects I maintain.
If I open a PR to cherry-pick this commit into the release branch, release-3.4. Would it be accepted?
We can take a PR for 3.4 and see if anything else comes in over the next few days to go along with it
TypeScript Version: Version 3.4.0-dev.20190329
Search Terms: "debug failure getArgumentArityError"
Code
Expected behavior:
c()
can be called as eitherc('a', 'foo')
orc('b', 'foo', 3)
(not necessarily fully type-checked).Actual behavior: Crash:
Related Issues: Lots of debug failures, but none that seem relevant.