Remove ‘@throws AssertionError’ KDoc from Assertion Functions

[jGleitz]

As discussed in #714, those docs where too vague to be actually helpful.

[codecov]

Codecov Report

Merging #742 (7a83fe9) into master (3508b57) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #742   +/-   ##
=========================================
  Coverage     87.93%   87.93%           
  Complexity       16       16           
=========================================
  Files           936      936           
  Lines          8412     8412           
  Branches        390      390           
=========================================
  Hits           7397     7397           
  Misses          940      940           
  Partials         75       75           

Flag	Coverage Δ	Complexity Δ
bbc	78.73% <ø> (ø)	0.00 <ø> (ø)
bc	57.20% <ø> (ø)	0.00 <ø> (ø)
current	59.59% <ø> (ø)	0.00 <ø> (ø)
current_windows	58.02% <ø> (ø)	0.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ	Complexity Δ
...h/tutteli/atrium/api/fluent/en_GB/anyAssertions.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
...tutteli/atrium/api/fluent/en_GB/arrayAssertions.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
...m/api/fluent/en_GB/charSequenceContainsCreators.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
...nt/en_GB/charSequenceContainsCreatorsDeprecated.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
...li/atrium/api/fluent/en_GB/collectionAssertions.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
...li/atrium/api/fluent/en_GB/comparableAssertions.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
...tteli/atrium/api/fluent/en_GB/featureAssertions.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
.../tutteli/atrium/api/fluent/en_GB/fun0Assertions.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
...teli/atrium/api/fluent/en_GB/iterableAssertions.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
...fluent/en_GB/iterableContainsInAnyOrderCreators.kt	100.00% <ø> (ø)	0.00 <0.00> (ø)
... and 69 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3508b57...831d279. Read the comment docs.

[robstoll]

@jGleitz I change my mind, sorry. I prefer if this commit does not contain changes to deprecated APIs, I am going to remove them in v0.16.0. Can you please revert those changes

[jGleitz]

Is it a problem if this does contain changes to deprecated APIs? I did all changes with search + replace. While it’s easy to roll that back for files of deprecated projects, finding all deprecated methods would be a lot of manual work.

If those functions will be deleted anyway, why does it matter if we change them in this PR?

[robstoll]

It is enough to revert all changes in path misc/deprecated, you don't need to search for methods in api-fluent or api-infix.
I prefer to have a clean history for traceability purposes. The changes to the deprecated API is just noise in this case.

[jGleitz]

sure, no problem! Done.

[robstoll]

Fixed the problems myself. Thanks for the PR 🙂, looking forward to the others