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

define-implicit defines syntax and not procedures #107

Open
wilbowma opened this issue May 27, 2020 · 5 comments
Open

define-implicit defines syntax and not procedures #107

wilbowma opened this issue May 27, 2020 · 5 comments

Comments

@wilbowma
Copy link
Owner

Constructors with implicit arguments are syntax and cannot be passed as values. This is a bit of a problem, as all constructors should be procedures.

@stchang
Copy link
Collaborator

stchang commented May 28, 2020

The function with implicit args would have to cooperate with #%app somehow.

It's doable, but then I think define-implicit would have to be part of the core and not a library?

@wilbowma
Copy link
Owner Author

wilbowma commented May 28, 2020

The library could extend #%app too, right?

@stchang
Copy link
Collaborator

stchang commented May 28, 2020

Yes, that might be ok but we could run into the diamond problem if a program uses this and another library that overloads #%app.

@wilbowma
Copy link
Owner Author

Yeah, but then we could make a choice about whether to include it in the "core" to avoid diamond problems or not. In general, I want the code to enable as much independence as possible, but in the end I imagine we'll have a set of features that are included in #lang cur, and only people doing weird things or experiments would have reason to reach under #lang cur and avoid implicits, e.g.

@stchang
Copy link
Collaborator

stchang commented May 28, 2020

Sounds reasonable.

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