Sjmarf to Programmer [email protected] • 6 months agoJavaScriptsh.itjust.worksimagemessage-square86fedilinkarrow-up1754arrow-down127
arrow-up1727arrow-down1imageJavaScriptsh.itjust.worksSjmarf to Programmer [email protected] • 6 months agomessage-square86fedilink
minus-squareVictorlink21•6 months agoSo there’s yet another level of quirkery to this bullshit then, it seems. 😆 Nice digging! 🤝 I also noticed that if you surround the curlies with parentheses, you get the same again: > eval('{} + []') 0 > eval('({}) + []') '[object Object]'
minus-square@[email protected]linkfedilink10•6 months agoYep, parentheses force {} to be interpreted as an expression rather than a block — same reason why IIFEs have !function instead of just function.
minus-squareVictorlink1•edit-26 months agoI thought IIFE’s usually looked like (function (...params) {})(...args). That’s not the latest way? To be honest I never used them much, at least not after arrow functions arrived.
So there’s yet another level of quirkery to this bullshit then, it seems. 😆 Nice digging! 🤝
I also noticed that if you surround the curlies with parentheses, you get the same again:
> eval('{} + []') 0 > eval('({}) + []') '[object Object]'Yep, parentheses force
{}to be interpreted as an expression rather than a block — same reason why IIFEs have!functioninstead of justfunction./me goes back to get second folding chair.
I thought IIFE’s usually looked like
(function (...params) {})(...args). That’s not the latest way? To be honest I never used them much, at least not after arrow functions arrived.