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

Fix compile time set cardinality #7558

Merged
merged 1 commit into from
Apr 10, 2018
Merged

Fix compile time set cardinality #7558

merged 1 commit into from
Apr 10, 2018

Conversation

GULPF
Copy link
Member

@GULPF GULPF commented Apr 10, 2018

The issue was that duplicates in set literals are never discarded, so just counting the elements gives the wrong result.

Fixes #7555

@Araq Araq merged commit 427490a into nim-lang:devel Apr 10, 2018
@narimiran narimiran mentioned this pull request Apr 11, 2018
4 tasks
Copy link
Member

@timotheecour timotheecour left a comment

Choose a reason for hiding this comment

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

@GULPF FYI

2, 3, 3, 4, 3, 4, 4, 5, 3, 4, 4, 5, 4, 5, 5, 6,
2, 3, 3, 4, 3, 4, 4, 5, 3, 4, 4, 5, 4, 5, 5, 6,
3, 4, 4, 5, 4, 5, 5, 6, 4, 5, 5, 6, 5, 6, 6, 7
]
Copy link
Member

Choose a reason for hiding this comment

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

@GULPF

  • how was this generated? (i'm assuming not by hand...)
  • could this be generated via CTFE?
  • if not generated by CTFE, at least needs a test that tries all int8 values

Copy link
Member Author

@GULPF GULPF Apr 11, 2018

Choose a reason for hiding this comment

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

I generated it with some quick & dirty code that I didn't want to keep around forever. I agree that it would be better to write some proper code and generate it at compile time, since it's now basically impossible to verify it by just reading it. However, it doesn't really make much of a difference. This table only needs to be verified once, because it will never ever change (but as a counter point, I have added hard-to-verify constants that are wrong before).

Copy link
Member

Choose a reason for hiding this comment

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

ok how about at least adding the quick and dirty code in a comment in that function? better than nothing IMO

Copy link
Member

Choose a reason for hiding this comment

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

This table only needs to be verified once, because it will never ever change

Unfortunately it wasn't verified at all afaict. :-) Please use compile-time evaluation for this.

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.

3 participants