Integer Set Token Parser
Parse a brace-delimited finite integer set, sorting and coalescing duplicates; only strict integer tokens and commas are accepted.
Description
Parse a brace-delimited finite integer set, sorting and coalescing duplicates; only strict integer tokens and commas are accepted.
A simple integer-set token can be parsed into unique sorted values. Braces and commas provide its entire grammar.
When to use this tool
Parse a brace-delimited finite integer set, sorting and coalescing duplicates; only strict integer tokens and commas are accepted.
- Prepare the supplied token fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter token. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.values. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Accept brace-enclosed signed digit tokens separated by commas, or empty braces. Parse integers within plus or minus one billion, deduplicate numeric values and sort ascending.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| token | token. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.values | The values list in the ordering and representation described above. |
{
"input": {
"token": "{3,-1,3}"
},
"output": {
"result": {
"values": [
-1,
3
]
}
}
}Limitations and assumptions
- Whitespace, ranges and nested sets are unsupported. Leading zeros and explicit plus signs are accepted but not retained in the numeric output.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a parser for the actual target format when the task requires CSV, shell, URL, calendar or filesystem semantics. These tools implement the specific small grammars stated here, without adding those surrounding conventions.
References
Similar or alternative tools
- Integer Set Token Formatter
Format finite bounded integer values as a canonical sorted brace-delimited set token, omitting duplicate values.
- Balanced Parenthesis Token Splitter
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.