Unexpected behaviour when logging out 'undefined'
mattgrande opened this issue · comments
Steps to reproduce
- Go the the repl
- Enter this:
const z = [null, undefined]
console.log(z)
Expected result
You should see [null, undefined]
in the right-hand side
Actual result
You see [null, null]
Browser: Chrome 59.0.3071.115
OS: OSX 10.12.5 (Sierra)
Kinda strange; I'm mostly just curious if others have seen this issue.
yeah that is strange. It appears to be just in the way console.log
works. If you just do:
const z = [null, undefined]
z;
the right side of the repl responds with [null, undefined]
. Since it evaluates correctly, this doesn't strike me as a crisis, just another hairy js edge.