Thanks Caitlin for the workaround ;)

However, as you can note, to write the following is not that much
praticabile and readable:

    ${()=>{
      //code here
    }()}

At least, the *do *keyword will improve the situation with i.e:

    ${do {
      //code here
    }}

PS: Is w/ or w/o the curly braces after the *do* keyword (?)


Hope to see news about the 'do' keyword adoption or something even better
in the early future! :D
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20160111/907d5197/attachment.html>

Thanks Caitlin for the workaround ;)

However, as you can note, to write the following is not that much
praticable and readable:

    ${()=>{
      //code here
    }()}

At least, the *do *keyword will improve the situation with i.e:

    ${do {
      //code here
    }}


Hope to see news about the 'do' keyword adoption or something even better
in the early future! :D

Thanks Caitlin for the workaround ;)

However, as you can note, to write the following is not that much
praticable and readable:

    ${()=>{
      //code here
    }()}

At least, the *do *keyword will improve the situation with i.e:

    ${do {
      //code here
    }}

PS: Is w/ or w/o the curly braces after the *do* keyword (?)


Hope to see news about the 'do' keyword adoption or something even better
in the early future! :D