Could it be doable to add a separate new property or something to a function that attaches it's preceding comment content or is a "verbose" toString alternative.
- Matthew Robb On Mon, Apr 18, 2016 at 11:40 AM, Andy Earnshaw <[email protected]> wrote: > I imagine there's code in the wild that predates function.name, looking > something like this: > > var fooName = foo.toString().match(/^function (\w+)/)[1]; > > If a newer browser adds a preceding comment to the function then this code > will break. The top voted answer to a question[1] on Stack Overflow would > break if the comment contained the string 'function '. > > [1]: http://stackoverflow.com/q/2648293 > > On Sun, 17 Apr 2016 at 11:07 Isiah Meadows <[email protected]> wrote: > >> I don't like the idea of including preceding comments in >> `Function.prototype.toString` itself on grounds it's harder to parse for >> other related reasons. >> >> As for anything including preceding comments, I'd be happy with something >> somewhat independent, as long as it's not requiring JSDoc to be parsed. Not >> that I have issues with that documentation format, but I don't think it >> should be in the spec itself. >> >> On Sat, Apr 16, 2016, 13:29 Jordan Harband <[email protected]> wrote: >> >>> As I see it, the primary purpose of the `Function#toString` proposal is >>> to document what browsers already do, and tighten it down so they can't >>> deviate further (which some browsers already have begun to do with "class", >>> for example). >>> >>> "Preceding comments" would be a very hard thing to specify without >>> unduly blessing an arbitrary documentation pattern, especially one that >>> isn't universally considered to be a good thing. >>> >>> Reflection methods on functions are certainly a potential separate >>> proposal, if you can make a compelling argument that it's a good idea to >>> reflect on functions in this manner. >>> >>> On Sat, Apr 16, 2016 at 9:42 AM, Marius Gundersen <[email protected]> >>> wrote: >>> >>>> Would it not be better to expose the names (and default values, >>>> destructurings, etc) of the function arguments using reflection? For >>>> example, Reflection.arguments(Math.max).then this method can return any >>>> JSDoc it is able to parse. >>>> On 16 Apr 2016 16:53, "Caitlin Potter" <[email protected]> wrote: >>>> >>>>> How would that interact with angular.js' Function.prototype.toString >>>>> parsing? Seems like doing that could break some content, even if it were >>>>> useful >>>>> >>>>> On Apr 16, 2016, at 10:48 AM, Axel Rauschmayer <[email protected]> >>>>> wrote: >>>>> >>>>> Regarding this proposal: >>>>> https://github.com/tc39/Function-prototype-toString-revision >>>>> >>>>> Wouldn’t it make sense to include a preceding JSDoc-style comment in a >>>>> function’s (or method’s) `[[SourceText]]` value? Conceptually it is a part >>>>> of the function and it could be used to implement a REPL `help()` >>>>> function. >>>>> >>>>> -- >>>>> Dr. Axel Rauschmayer >>>>> [email protected] >>>>> rauschma.de >>>>> >>>>> _______________________________________________ >>>>> es-discuss mailing list >>>>> [email protected] >>>>> https://mail.mozilla.org/listinfo/es-discuss >>>>> >>>>> >>>>> _______________________________________________ >>>>> es-discuss mailing list >>>>> [email protected] >>>>> https://mail.mozilla.org/listinfo/es-discuss >>>>> >>>>> >>>> _______________________________________________ >>>> es-discuss mailing list >>>> [email protected] >>>> https://mail.mozilla.org/listinfo/es-discuss >>>> >>>> >>> _______________________________________________ >>> es-discuss mailing list >>> [email protected] >>> https://mail.mozilla.org/listinfo/es-discuss >>> >> _______________________________________________ >> es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss >> > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
