ObjFW  History of src/OFHMAC.h of a13251499a58bde6

Before, -[digest] would do the final calculation, however, this would
mean a property modifies state, which is bad. file: [618167fc85] check-in: [82801897d3] user: js, branch: trunk, size: 3932 [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: [5ff44e63ad] check-in: [e629dc83a9] user: js, branch: trunk, size: 3892 [annotate] [blame] [check-ins using] [diff]

This allows ABI stability with the fragile ABI. file: [c85420d05a] check-in: [496695d778] user: js, branch: trunk, size: 3465 [annotate] [blame] [check-ins using] [diff]

This improves Swift compatibility. file: [0c8ac23177] check-in: [f3ccf14461] user: js, branch: trunk, size: 3389 [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: [aaa867eca5] check-in: [2f4e0df8be] user: js, branch: trunk, size: 3435 [annotate] [blame] [check-ins using] [diff]

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

This changes retaining behavior, meaning properties are not returned
retained and autoreleased anymore, so a property returned from a getter
now needs to be manually retained and autoreleased before calling the
setter. However, this is rarely the case and not using atomic improves
performance. file: [60c34cd9f4] check-in: [0a73af49f0] user: js, branch: trunk, size: 3330 [annotate] [blame] [check-ins using] [diff]

Forgot to add 2017, even though I already did quite some changes in
2017. file: [978ea49e23] check-in: [44f45c2e35] user: js, branch: trunk, size: 3327 [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: [682e9b5139] check-in: [19f7dc67af] user: js, branch: trunk, size: 2485 [annotate] [blame] [check-ins using] [diff]