Sjmarf@sh.itjust.works to Programmer Humor · 5 months agoJavaScriptsh.itjust.worksimagemessage-square88fedilinkarrow-up1763arrow-down128
arrow-up1735arrow-down1imageJavaScriptsh.itjust.worksSjmarf@sh.itjust.works to Programmer Humor · 5 months agomessage-square88fedilink
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up21·5 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-squarePoolloverNathanlinkfedilinkarrow-up10·5 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-squaredejected_warp_core@lemmy.worldlinkfedilinkarrow-up3·5 months ago/me goes back to get second folding chair.
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up1·edit-25 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.