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

Combine Builtins and Prelude #766

Open
brprice opened this issue Nov 7, 2022 · 0 comments
Open

Combine Builtins and Prelude #766

brprice opened this issue Nov 7, 2022 · 0 comments
Assignees
Labels
core Core issue easy Should be straightforward to fix

Comments

@brprice
Copy link
Contributor

brprice commented Nov 7, 2022

For historical reasons we have three places where we pre-define some types and/or terms: Builtins, Prelude and Primitives. The Primitives are special, since they are special support for non-algebraic types (Integer etc), so they should be left separate. However, Builtins and Prelude are both entirely user-definable, and their only reason for existence is to make the testsuite easier and to seed new programs. They should probably be combined (i.e. merge builtins into prelude).

(Somewhat related: #344 (comment))

@brprice brprice added the triage This issue needs triage label Nov 7, 2022
@dhess dhess added core Core issue and removed triage This issue needs triage labels Nov 7, 2022
@dhess dhess added this to the Primer 0.8 milestone May 9, 2023
@dhess dhess added the easy Should be straightforward to fix label Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Core issue easy Should be straightforward to fix
Projects
None yet
Development

No branches or pull requests

2 participants