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 has been archived by the owner on Dec 11, 2021. It is now read-only.
Both have pros and cons. Function expression leads to better consistency (you cannot use function declaration for function composition, currying etc.), but it’s not hoisted (so it requires specific ordering of functions). Also you cannot write export default const foo = () => { }, but I consider this as insignificant.
The text was updated successfully, but these errors were encountered:
I think I am willing to give up some consistency in favor of preventing some WTF moments caused by hoisting.
My personal opinion: top-level function keyword helps me with code readability.
Let's keep this open in case someone else wants to chime in.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Both have pros and cons. Function expression leads to better consistency (you cannot use function declaration for function composition, currying etc.), but it’s not hoisted (so it requires specific ordering of functions). Also you cannot write
export default const foo = () => { }
, but I consider this as insignificant.The text was updated successfully, but these errors were encountered: