Sjmarf to Programmer Humor@programming.dev • 9 days agoJavaScriptsh.itjust.worksimagemessage-square87fedilinkarrow-up1751arrow-down129
arrow-up1722arrow-down1imageJavaScriptsh.itjust.worksSjmarf to Programmer Humor@programming.dev • 9 days agomessage-square87fedilink
minus-squareVictorlinkfedilink20•9 days 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@PoolloverNathan@programming.devlinkfedilink10•9 days agoYep, parentheses force {} to be interpreted as an expression rather than a block — same reason why IIFEs have !function instead of just function.
minus-square@dejected_warp_core@lemmy.worldlinkfedilink3•8 days ago/me goes back to get second folding chair.
minus-squareVictorlinkfedilink1•edit-28 days 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.