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

Discussion: Disambiguation of requires #2891

Closed
jwaldrip opened this issue Jun 21, 2016 · 2 comments
Closed

Discussion: Disambiguation of requires #2891

jwaldrip opened this issue Jun 21, 2016 · 2 comments

Comments

@jwaldrip
Copy link

This is just to start a dialog. I love crystal and what the team has done thus far.

One thing I dislike about ruby is the ambiguity of the require syntax. I don't think requires should become global objects or constants. You should be able to control the assignment of other dependencies in the language. As someone who is debugging a certain file, I believe it is much easier to chase the rabbit when your dependencies are specified locally.

Other languages where this exists:

  • Go
  • Python
  • Node.js
  • ES6
@jwaldrip jwaldrip changed the title Discussion: Disambiguity of requires Discussion: Disambiguation of requires Jun 21, 2016
@jhass
Copy link
Member

jhass commented Jun 22, 2016

See #140, #265, #1146, #2090, to some degree #1446 and crystal-lang/shards#16

I think we discussed this pretty throughout by now and I still feel like it doesn't fit into some of the core language design decisions already taken, at all.

@ysbaddaden
Copy link
Contributor

Yes, closing as duplicate of #140 along with this statement by @asterite:

we won't change the require system. We might introduce a concept similar to refinements if we later find the need for it.

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

No branches or pull requests

3 participants