Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Won't you lose the convenience of lexical scoping when creating first-class functions? #15

Open
AnthonyMastrean opened this issue Aug 19, 2013 · 2 comments

Comments

@AnthonyMastrean
Copy link

No description provided.

@max-mapper
Copy link
Owner

its a tradeoff, relying too heavily on lexical scoping makes things harder
to understand and harder to modularize (you cant share lexical scope
between modules). a nice side effect of decoupled functions is the explicit
interface and lack of magical-seeming shared variables

sometimes its nice to put a function inside another function to take
advantage of the lexical scope convenience, but I personally go more than 1
level deep

On Mon, Aug 19, 2013 at 1:33 PM, Anthony Mastrean
notifications@github.comwrote:


Reply to this email directly or view it on GitHubhttps://github.com//issues/15
.

@AnthonyMastrean
Copy link
Author

Thanks for the comment. I've heard the same elsewhere... it depends!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants