> there isn't much difference from the `do expression`, actually, it might be
> worse since it looks confusing. if it can not be omitted, I'd rather stay
> with `do`.
I thought omitting additional brackets(`var foo = = if (cond) { bar } else {
baz }`) was most sweet spot in this proposal than d
ambiguous case
```
let x = {
// statements here?
label: ’value'
};
```
> 2016. 10. 30., 오후 5:54, JongChan Choi 작성:
>
> OMG sweet! I love it.
> then how it’ll be formed when mixed with labeled statement?
>
>> 2016. 10. 30., 오후 3:15, Yongxu Ren > <
OMG sweet! I love it.
then how it’ll be formed when mixed with labeled statement?
> 2016. 10. 30., 오후 3:15, Yongxu Ren 작성:
>
> Yes, it does the exact same thing.
> I think using = and operators is a bit cleaner than 'do'.
> However, The biggest advantage for this feature is you can write functio
3 matches
Mail list logo
