ObjFW  History of src/OFHMAC.m of bd2d723910df5ff3

Before, -[digest] would do the final calculation, however, this would
mean a property modifies state, which is bad. file: [2ceebc7fc2] check-in: [82801897d3] user: js, branch: trunk, size: 4811 [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: [8b2647f9b8] check-in: [e629dc83a9] user: js, branch: trunk, size: 4644 [annotate] [blame] [check-ins using] [diff]

Instead, explicitly declare them, as OF_ASSUME_NONNULL_{BEGIN,END} does
not apply to implicit return types. This means that after this commit,
all init methods have a nonnull return type, as they should have. file: [7f94007b12] check-in: [2f4e0df8be] user: js, branch: trunk, size: 3680 [annotate] [blame] [check-ins using] [diff]

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

Forgot to add 2017, even though I already did quite some changes in
2017. file: [2e98081b44] check-in: [44f45c2e35] user: js, branch: trunk, size: 3592 [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: [9c331f3be4] check-in: [19f7dc67af] user: js, branch: trunk, size: 2985 [annotate] [blame] [check-ins using] [diff]