You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 25, 2022. It is now read-only.
This spec is now completely outdated as of the last meeting. I will be entirely rewriting it (again) to reflect the committee's new wishes, which are to preserve a slice of source text from the beginning of the first token of the appropriate structure to the end of the last token. This should address your concern about function names. If so, please close.
I see the following NOTE at the bottom of the new spec:
"NOTE 2: Do we preserve function name? If so, do unnamed FDs and CDs in export default position cause problems here?"
I think the spec needs to specify this, since the presence (or lack) of function names has semantic meaning. Consider:
Similarly, for named expressions, including the name is important in case the function wishes to recurse.
The text was updated successfully, but these errors were encountered: