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

eval: Fix any's wrapping any's #42

Merged
merged 2 commits into from
Oct 20, 2022
Merged

eval: Fix any's wrapping any's #42

merged 2 commits into from
Oct 20, 2022

Conversation

juliaogris
Copy link
Member

@juliaogris juliaogris commented Oct 20, 2022

Fix any's wrapping any's so that any only ever contains a
non-any type. We have added two test cases that failed before the code fix.

Sneak in a make ci dependency reorder so that linter errors surface earlier.

@juliaogris juliaogris force-pushed the eval-any-fix branch 2 times, most recently from b05cbee to a5cd042 Compare October 20, 2022 00:44
@github-actions
Copy link

github-actions bot commented Oct 20, 2022

firebase-deployment: https://evy-lang--42-o3su607s.web.app (a9e883a)

@juliaogris juliaogris force-pushed the eval-any-fix branch 2 times, most recently from 1337ceb to d164154 Compare October 20, 2022 00:56
Reorder `make ci` dependences to float more common errors early. At this
stage the linter catches me out the most often and I'd like to know
about this before running the rather slow tiny go build and tests.
Fix `any`'s wrapping `any`'s so that `any` only ever contains a
non-`any` type. We have added two test cases that failed before the
code fix in the evaluator.
Copy link
Contributor

@camh- camh- left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥗

@juliaogris juliaogris merged commit 04ebf29 into master Oct 20, 2022
@juliaogris juliaogris deleted the eval-any-fix branch October 20, 2022 02:46
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

Successfully merging this pull request may close these issues.

None yet

2 participants