-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update flow to 0.180.0 #8201
Update flow to 0.180.0 #8201
Conversation
} else if (alias.fileName) { | ||
alias = alias.fileName; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Flow said that this is unreachable type-wise. And this branch was indeed never reached in the tests. So either it really is dead, or we don't test this at all.
Benchmark ResultsKitchen Sink ✅
Timings
Cold Bundles
Cached BundlesNo bundle changes detected. React HackerNews ✅
Timings
Cold BundlesNo bundle changes detected. Cached BundlesNo bundle changes detected. AtlasKit Editor ✅
Timings
Cold BundlesNo bundle changes detected. Cached BundlesNo bundle changes detected. Three.js ✅
Timings
Cold BundlesNo bundle changes detected. Cached BundlesNo bundle changes detected. |
shouldScopeHoist = false, | ||
sourceMap, | ||
loc, | ||
}: EnvironmentOpts = {...null}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is weird. What's going on here? All the properties are optional right, so why null?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not about the properties, it's literally only about exact/inexact/unsealed objects: facebook/flow#7424
https://flow.org/try/#0DYUwLgBAHgXBDeAfRBfCBeBKDcAoUkAnnPGpqXgRAF4nJkIB0zAdgK7DA5A
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's super weird when all the properties are optional. Therefore an empty object should be valid. I guess {...null}
has some additional runtime overhead. sigh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, {/*:: ...null */}
works as well, and doesn't do anything at runtime. I've also replaced all preexisting occurrences of {...null}
with the comment version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol wow
...