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.

Sign up for GitHub

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

Jump to bottom

Create idiomatic variant #6

Closed
flaviut opened this issue Mar 4, 2015 · 2 comments · Fixed by #8
Closed

Create idiomatic variant #6

flaviut opened this issue Mar 4, 2015 · 2 comments · Fixed by #8
Labels
RFC
Milestone
Release 1.0.0

Comments

@flaviut
Copy link
Owner

flaviut commented Mar 4, 2015

@Araq has pointed out that nre uses exclusive upper bounds, when most Nim code uses inclusive upper bounds. There should be a version of nre to use inclusive upper bounds.
@oprypin
Copy link
Collaborator

oprypin commented Mar 4, 2015

One thing that I feel strongly against is the use of Nim's .. for exclusive upper bounds here.

@oprypin
Copy link
Collaborator

oprypin commented Apr 9, 2015

You should just turn everything to inclusive upper bounds 😐

@oprypin oprypin mentioned this issue Apr 9, 2015
Merged
@flaviut flaviut closed this as completed in #8 Apr 9, 2015
@oprypin oprypin mentioned this issue Apr 10, 2015
Closed
12 tasks
@oprypin oprypin added the RFC label Apr 12, 2015
@flaviut flaviut modified the milestone: Release 1.0.0 May 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
RFC
Projects
None yet
Milestone
Release 1.0.0
Development

Successfully merging a pull request may close this issue.

Change capture upper bounds to inclusive
2 participants
@oprypin @flaviut