all_asserts 2.3.1

A crate for multiple types of asserts that don't exist in the standard library
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

# Changelog

All changes in this project will be noted in this file.

## Version 2.3.1 [2022-02-02]

- (Possibly breaking): The crate now calls `contains` from `RangeBounds` using FQS for disambiguation.
  If there was a crate local trait having a definition of `contains` matching the same prototype
  signature, then this should be considered a breaking change since the intended trait method is now
  called instead of erroneously calling the crate local definition. Else, it's completely fine.

## Version 2.3.0 [2021-09-13]

> This release doesn't introduce breaking changes

## Additions

- Added the `assert_true`, `assert_false`, `assert_near` macros

## Version 2.2.0 [2020-11-10]

> This release doesn't introduce breaking changes

Added `debug_*` variants for macros

## Version 2.1.0 [2020-06-25]

> This release doesn't introduce breaking changes

Enable adding messages to the `assert_range!` and `assert_nrange!` outputs.

Example:

```rust
assert_nrange!((1.0..2.0), 1.5, "Oops! 1.5 is in the interval [1.0,2.0)")
```

## Version 2.0.1 [2020-06-25]

> This release doesn't introduce breaking changes

Fix documentation issues

## Version 2.0.0 [2020-06-25]

> This release doesn't introduce breaking changes

Added new macros: `assert_range!` , `assert_nrange!`

## Version 1.0.1 [2020-06-18]

> This release doesn't introduce breaking changes

Fix issues with ownership and licensing

## Version 1.0.0 [2019-11-16]

> This release doesn't introduce breaking changes

First stable release

## Version 0.x.y

> These releases don't introduce any breaking changes