function definitions in object shorthand should generate named function definitions rather than anonymous functions

[nojvek]

Btw brilliant work on getting object shorthand

let logger = {
   log(str){
      console.log(str)
   }
};

generates

var logger = {
    log: function (str) {
        console.log(str);
    }
};

since it becomes an anonymous function, it doesn't stand out in stack traces. Emitting this would make debugging and stack traces a lot nicer.

var logger = {
    log: function log (str) {
        console.log(str);
    }
};

[DanielRosenwasser]

This might be related to #6433.

[Hotell]

I don't think this is a bug? It's how it should work according to MDN, but I may be wrong ofc https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Method_definitions

[nojvek]

Babel does this too. The stack traces are super helpful. Es6 outputted code in chrome does this too.

…

On Fri, Mar 24, 2017 at 5:11 AM Martin Hochel ***@***.***> wrote: I don't think this is a bug? It's how it should work according to MDN, but I may be wrong ofc https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Method_definitions — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6757 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA-JVGu6kIWvXqLyzHAn4BpWXHoiEFUYks5ro7MHgaJpZM4HP2CM> .

[grundmanise]

@Hotell Is right in regards to how it should be transpiled. Their names should be inferred due to the runtime semantics which are defined in the specs

[RyanCavanaugh]

This doesn't seem like an important scenario for modern JS development - folks can either target ES6 which is supported basically everywhere, or use an alternate transpiler with stricter adherence semantics if this is important for their scenario.