ObjFW  History of src/OFCryptoHash.h of 951f530aeee0b50e

Before, -[digest] would do the final calculation, however, this would
mean a property modifies state, which is bad. file: [21f208b184] check-in: [82801897d3] user: js, branch: trunk, size: 3386 [annotate] [blame] [check-ins using] [diff]

With this property, it's possible to specify whether the memory should
be protected from swapping or not. This makes it easier for e.g. the
crypto hash classes: They can now just always use OFSecureData without
wasting unswappable memory if it's not needed. file: [ef88b31b2d] check-in: [e629dc83a9] user: js, branch: trunk, size: 3352 [annotate] [blame] [check-ins using] [diff]

This improves Swift compatibility. file: [2634ee9f93] check-in: [a2e849c681] user: js, branch: trunk, size: 2640 [annotate] [blame] [check-ins using] [diff]

This improves Swift compatibility. file: [ab2417692f] check-in: [f3ccf14461] user: js, branch: trunk, size: 2485 [annotate] [blame] [check-ins using] [diff]

Casts are now written like types in variable declarations. file: [fb07c27325] check-in: [4af49a13c3] user: js, branch: trunk, size: 2500 [annotate] [blame] [check-ins using] [diff]

Forgot to add 2017, even though I already did quite some changes in
2017. file: [14a9d18645] check-in: [44f45c2e35] user: js, branch: trunk, size: 2498 [annotate] [blame] [check-ins using] [diff]

While in practice they are usually the same, the C standard says that
only char does not have any alignment requirements. As (u)int*_t is
defined to be an integer type of the specified size, it does not mean
(u)int8_t needs to be char. file: [91b722cbde] check-in: [19f7dc67af] user: js, branch: trunk, size: 2258 [annotate] [blame] [check-ins using] [diff]