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

Range resolver #28

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Range resolver #28

wants to merge 2 commits into from

Conversation

nahratzah
Copy link
Collaborator

I'm not entirely sure about the configuration form, yet.

Currently, it's:

tupleKey = 1..100

which generates the numbers 1, 2, 3, ..., 98, 99, 100.
Note the absence of square brackets.

Numbers must be valid signed integers (INT_MIN to INT_MAX).
The code has been tested to do the right thing with INT_MIN and/or INT_MAX.
Although supplying the entire range of integers does require a lot of memory.


I'm debating if I should enable this in tuples, for example:

(key1, key2) = [
    ("somehost",  6000..6009),
    ("otherhost", 6010..6019),
    ...
]

which might be a nice way to supply port ranges, for instance.


I'm debating if I should enable this in lists too:

tupleKey = [ 80, 443, 8000..8080 ]

which might be a nice way to add a lot of numbers quickly.

Ariane van der Steldt added 2 commits September 10, 2016 12:14
- RangeResolver(0, 0) -- 0..0, range containing single 0.
- RangeResolver(0, 1) -- 0..1, range containing 0, 1.

While here, implement tests for RangeResolver.
Not sure if this should be the final form...
@nils-
Copy link
Contributor

nils- commented Oct 19, 2016

I like the idea of being able to supply a range, especially as it's less typing.

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.

2 participants