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
/**
Binary selection trait that make it possible to implement traits differently on disjoint types.
The only two implementing types are [`True`] and [`False`].
This is used to
[circumvent a compiler limitation and implement traits differently
on disjoint types](https://github.com/rust-lang/rfcs/pull/1672#issuecomment-1405377983).
See [`IsAtomic`] for an example.
*/
/// [`BooleanSelector`] version of [`true`], this is an empty struct used only for
/// type system bounds
/// [`BooleanSelector`] version of [`false`], this is an empty struct used only for
/// type system bounds
/// A trait with an associated [`BooleanSelector`] type specifying whether the type is atomic.
/// It can be used to implement traits differently for atomic and non-atomic types.
/// See the `atomic_data` example.
/// A generic trait with an associated boolean, which can be used to do
/// specialization. See the example `atomic_data` for more information.
/// Non zero variants of primitives types for enum optimizations
/// A trait with an associated [`BooleanSelector`] type specifying whether an integer type is signed.
/// It can be used to implement traits differently for signed and unsigned types.
/// See the `atomic_data` example.
/// A trait with an associated [`BooleanSelector`] type specifying whether an type is a float number.
/// It can be used to implement traits differently for float and non float types.
/// See the `atomic_data` example.
/// A trait with an associated [`BooleanSelector`] type specifying whether an type is an Integer number.
/// It can be used to implement traits differently for integer and non integer types.
/// See the `atomic_data` example.