-
Notifications
You must be signed in to change notification settings - Fork 170
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
New scoping system #719
Comments
Oh gosh I'd have to really go back and think about this. I believe the main issue is that we ought to be able to keep the 'base' scope as an existential, but for whatever reason, when I first wrote beam, the compiler was unable to match existentials and allow typechecking to pass. It probably does at this point. |
Thanks for remembering, @tathougies. On a similar note, here and a few other places in beam I would have used data kinds (don't need arbitrary types in our scopes do we?). Do you have thoughts on that? |
Yeah, the scoping system could definitely be replaced with data kinds. Keep in mind Haskell looked a lot different when I first wrote beam :) |
@tathougies I believe it, but I also think I don't know just how far back the prehistory of beam goes :). |
Originally posted by @tathougies in #652 (comment)
What would this look like? More data kinds? Something more radical?
The text was updated successfully, but these errors were encountered: