int-interval-set 0.3.4

Integer half-open interval set structures built on top of int-interval.
Documentation
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
# int-interval-set

[![Crates.io](https://img.shields.io/crates/v/int-interval-set.svg)](https://crates.io/crates/int-interval-set)
[![Documentation](https://docs.rs/int-interval-set/badge.svg)](https://docs.rs/int-interval-set)
[![License](https://img.shields.io/crates/l/int-interval-set.svg)](https://crates.io/crates/int-interval-set)
[![CodSpeed](https://github.com/jcfangc/int-interval-set/actions/workflows/codspeed.yml/badge.svg?branch=main)](https://github.com/jcfangc/int-interval-set/actions/workflows/codspeed.yml)


`int-interval-set` provides immutable canonical interval-set containers for
integer half-open intervals.

The crate is built around a single generic set type:

```rust
IntCOSet<I>
```

where:

```rust
I: IntCO
```

Concrete interval-set types such as `U8COSet` and `I32COSet` are now simple
type aliases.

The library no longer uses builders, concurrent mutable phases, or generated
set implementations.

Instead, interval sets are constructed directly from iterators and immediately
canonicalized into compact immutable arrays.

---

# Interval semantics

All intervals are half-open:

```text
[start, end_excl)
```

For example:

```text
[10, 20)
```

contains:

```text
10, 11, ..., 19
```

but does not contain:

```text
20
```

Intervals are canonicalized automatically during construction.

Adjacent intervals are merged:

```text
[0, 5) + [5, 10) -> [0, 10)
```

Overlapping intervals are also merged:

```text
[10, 20) + [15, 30) -> [10, 30)
```

The canonical invariant is:

```text
for every adjacent pair a, b:
    a.end_excl() < b.start()
```

This means canonical interval sets are:

- sorted;
- non-overlapping;
- non-adjacent;
- already merged.

---

# Core type

```rust
pub struct IntCOSet<I: IntCO>
```

Internally:

```rust
Arc<[I]>
```

is used as the immutable storage representation.

Cloning a set is therefore cheap.

---

# Provided aliases

Unsigned:

```rust
U8COSet
U16COSet
U32COSet
U64COSet
U128COSet
UsizeCOSet
```

Signed:

```rust
I8COSet
I16COSet
I32COSet
I64COSet
I128COSet
IsizeCOSet
```

These are aliases only:

```rust
pub type U8COSet = IntCOSet<U8CO>;
```

---

# Construction

Interval sets are usually constructed through `FromIterator`.

Example:

```rust
use int_interval::U8CO;
use int_interval_set::U8COSet;

let set: U8COSet = [
    U8CO::try_new(10, 20).unwrap(),
    U8CO::try_new(15, 30).unwrap(),
    U8CO::try_new(40, 50).unwrap(),
]
.into_iter()
.collect();

assert_eq!(
    set.as_slice(),
    &[
        U8CO::try_new(10, 30).unwrap(),
        U8CO::try_new(40, 50).unwrap(),
    ]
);
```

Parallel construction is also supported through Rayon:

```rust
use rayon::iter::{IntoParallelIterator, ParallelIterator};
use int_interval::U8CO;
use int_interval_set::U8COSet;

let set: U8COSet = vec![
    U8CO::try_new(0, 10).unwrap(),
    U8CO::try_new(10, 20).unwrap(),
]
.into_par_iter()
.collect();

assert_eq!(
    set.as_slice(),
    &[U8CO::try_new(0, 20).unwrap()]
);
```

---

# Basic accessors

```rust
set.interval_count();
set.is_empty();
set.as_slice();
set.iter_intervals();
```

Example:

```rust
assert_eq!(set.interval_count(), 2);

for interval in set.iter_intervals() {
    println!("{interval:?}");
}
```

---

# Predicate APIs

Predicate APIs answer yes-or-no questions.

```rust
set.contains_point(x);
set.contains_interval(query);
set.intersects_interval(query);
```

Example:

```rust
use int_interval::U8CO;

let query = U8CO::try_new(15, 25).unwrap();

assert!(set.intersects_interval(query));
assert!(!set.contains_interval(query));
```

---

# Search APIs

## Find interval containing a point

```rust
let hit = set.interval_containing_point(18);
```

Because sets are canonical, at most one interval can contain a point.

---

## Iterate intersecting intervals

```rust
let hits: Vec<_> = set
    .intervals_intersecting(
        U8CO::try_new(15, 45).unwrap()
    )
    .collect();
```

Example:

```text
set:   [10, 20), [30, 40)
query: [15, 35)

out:
  [10, 20), [30, 40)
```

---

# Interval-vs-set algebra

## Intersection

```rust
set.intersection_with_interval(query);
```

Example:

```text
set:   [10, 20), [30, 40)
query: [15, 35)

out:
  [15, 20), [30, 35)
```

---

## Union

```rust
set.union_with_interval(query);
```

Example:

```text
set:   [10, 20), [30, 40)
query: [20, 30)

out:
  [10, 40)
```

---

## Difference

```rust
set.difference_with_interval(query);
```

Example:

```text
set:   [10, 20), [30, 40), [50, 60)
query: [15, 55)

out:
  [10, 15), [55, 60)
```

---

## Symmetric difference

```rust
set.symmetric_difference_with_interval(query);
```

Example:

```text
set:   [10, 20), [30, 40)
query: [15, 35)

out:
  [10, 15), [20, 30), [35, 40)
```

---

# Set-vs-set algebra

## Intersection

```rust
left.intersection_with_set(&right);
```

---

## Union

```rust
left.union_with_set(&right);
```

---

## Difference

```rust
left.difference_with_set(&right);
```

---

## Symmetric difference

```rust
left.symmetric_difference_with_set(&right);
```

Example:

```text
left:  [0, 10), [20, 30)
right: [5, 15), [25, 35)

xor:
  [0, 5), [10, 15), [20, 25), [30, 35)
```

---

# Coverage APIs

Coverage APIs measure how much of a query interval is covered by the set.

```rust
set.covered_len_of(query);
set.uncovered_len_of(query);

set.coverage_ratio_f32_of(query);
set.coverage_ratio_f64_of(query);
```

Example:

```text
set:   [10, 20), [30, 40)
query: [15, 35)

covered:
  [15, 20), [30, 35)

covered length:
  10

query length:
  20

coverage ratio:
  0.5
```

---

# Complexity

Most query operations are logarithmic or linear in the number of matching
intervals.

Representative costs:

| Operation | Complexity |
|---|---|
| `contains_point` | `O(log n)` |
| `contains_interval` | `O(log n)` |
| `intersects_interval` | `O(log n)` |
| `intervals_intersecting` | `O(log n + k)` |
| `intersection_with_interval` | `O(log n + k)` |
| `union_with_interval` | `O(log n + n)` |
| `difference_with_interval` | `O(log n)` to `O(n)` |
| `intersection_with_set` | `O(n + m)` |
| `union_with_set` | `O(n + m)` |
| `difference_with_set` | `O(n + m)` |
| `symmetric_difference_with_set` | `O(n + m)` |

where:

```text
n = self interval count
m = other interval count
k = number of matching intervals
```

---

# Design goals

The crate prioritizes:

- immutable canonical representations;
- predictable interval algebra;
- low-overhead binary-search queries;
- generic implementations over all integer interval types;
- zero code generation;
- simple semantics and explicit APIs.