🤖 User test baselines have changed for refs/heads/master#36046
Conversation
c87b6d7 to
55e5dd8
Compare
55e5dd8 to
03359d5
Compare
|
I'll take a look. |
| node_modules/lodash/_baseClone.js(91,16): error TS2362: The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type. | ||
| node_modules/lodash/_baseClone.js(92,16): error TS2362: The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type. | ||
| node_modules/lodash/_baseClone.js(93,16): error TS2362: The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type. | ||
| node_modules/lodash/_baseClone.js(114,18): error TS2554: Expected 0 arguments, but got 1. |
There was a problem hiding this comment.
The type of function expressions in conditional expressions has changed. Might be ones that are initialisers of variable decls with jsdoc, not sure yet.
There was a problem hiding this comment.
Here's a repro. I guess we changed our rules for unioning signatures recently.
var noop = () => { };
/**
* @returns {void}
*/
var createSet = !!false ? noop : function(values) {
};
createSet(1) // error before, fine now
sandersn
left a comment
There was a problem hiding this comment.
Let's hold the change until I figure out which commit caused it. I'm not sure it's wrong, just unexpected to me.
| node_modules/lodash/_baseClone.js(91,16): error TS2362: The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type. | ||
| node_modules/lodash/_baseClone.js(92,16): error TS2362: The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type. | ||
| node_modules/lodash/_baseClone.js(93,16): error TS2362: The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type. | ||
| node_modules/lodash/_baseClone.js(114,18): error TS2554: Expected 0 arguments, but got 1. |
There was a problem hiding this comment.
Here's a repro. I guess we changed our rules for unioning signatures recently.
var noop = () => { };
/**
* @returns {void}
*/
var createSet = !!false ? noop : function(values) {
};
createSet(1) // error before, fine now|
It is #35659; only seems to affect JS signatures. |
sandersn
left a comment
There was a problem hiding this comment.
Talked to Anders and the new behaviour is fine; the old behaviour was random based on which function came first in the source file.
This test run was triggerd by a request on #33716
Please review the diff and merge if no changes are unexpected.
You can view the build log here.
cc @microsoft/typescript