WSL should not type-check functions in the standard library that it does not use #177
Comments
At 2017-09-20T21:19:11Z, fpizlo@apple.com wrote: |
At 2017-09-20T21:26:04Z, jfbastien@apple.com wrote: View in context: https://bugs.webkit.org/attachment.cgi?id=321367&action=review r=me
=== ?
Why?
=== ?
Why? |
At 2017-09-20T22:09:14Z, fpizlo@apple.com wrote:
Fixed.
arguments.length doesn't work in arrow functions.
Fixed.
Later phases resolve these directly sometimes (the compiler will say things like program.globalNameContext.get(Type, "void") and expect non-null). For example even if you compile "int foo() { return 42; }", we will resolve void just to make sure that int isn't the same as void - because if int was void then the return shouldn't return a value. Also if you compile "double foo() { return 42; }" we will also resolve int because "42" might be an int (we actually select double as 42's type but not before trying int). |
At 2017-09-20T22:41:17Z, fpizlo@apple.com wrote: |
At 2017-09-27T19:20:01Z, webkit-bug-importer@group.apple.com wrote: |
Migrated from https://bugs.webkit.org/show_bug.cgi?id=177269:
At 2017-09-20T21:13:53Z, fpizlo@apple.com wrote:
Patch forthcoming.
The text was updated successfully, but these errors were encountered: