ObjFW  History of src/OFSet.h of 4b635088b6be1934

While the idea sounds nice that the tag name is the class, this means the
serialization includes whether something is mutable or immutable. This means
doing as much as making something immutable changes the serialization, which
can then cause issues after being deserialized. file: [b6b0fc8990] check-in: [6ce0093f8d] user: js, branch: trunk, size: 7422 [annotate] [blame] [check-ins using] [diff]

Classes using lightweight generics should also use them for the
enumerator to allow stronger typing. file: [14327ba57e] check-in: [f0f38b0f42] user: js, branch: trunk, size: 8017 [annotate] [blame] [check-ins using] [diff]

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

This improves Swift compatibility. file: [62a20daa00] check-in: [f3ccf14461] user: js, branch: trunk, size: 7924 [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: [6c82eb5230] check-in: [2f4e0df8be] user: js, branch: trunk, size: 8193 [annotate] [blame] [check-ins using] [diff]

It does not work well enough yet: While creating a lot of noise, it
fails to even find many of the obvious cases. Depending on the static
analyzer seems to be the better approach for now. file: [28701b2ea5] check-in: [e47c219327] user: js, branch: trunk, size: 8123 [annotate] [blame] [check-ins using] [diff]

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

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

If the key starts with an @, the @ is stripped and the super method is
called. Otherwise, this returns the value for all objects / sets the
value for all objects. file: [be2d24001b] check-in: [ef8d57bd4e] user: js, branch: trunk, size: 8121 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [d3840fdbd2] check-in: [cec0f072f8] user: js, branch: 0.8, size: 7188 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [58c61ab64e] check-in: [2a27cf3000] user: js, branch: trunk, size: 7180 [annotate] [blame] [check-ins using] [diff]

Now that Clang switched to use _Nullable and _Nonnull instead of
__nullable / __nonnull, there is no longer a conflict with glibc, which
means we can just define _Nullable / _Nonnull to nothing if they are not
understood by the compiler (which did not work with __nullable /
__nonnull due to this conflict).

This also defines _Null_unspecified to nothing if unavailable. file: [b3a46a1679] check-in: [d526d938d7] user: js, branch: trunk, size: 7176 [annotate] [blame] [check-ins using] [diff]

Using __nonnull directly doesn't work on systems using glibc, as glibc
defines __nonnull as a parameterized define. While this does not fix the
problem of Clang introducing __nonnull even though it conflicts with
glibc, this at least means it's possible again to compile things with
versions of Clang that don't support __nonnull on systems with glibc. file: [cac22c2803] check-in: [b7097a67b6] user: js, branch: trunk, size: 7184 [annotate] [blame] [check-ins using] [diff]

This also removes "bool *stop" from some blocks where it does not make
sense. file: [a277fd200b] check-in: [e8473b9db8] user: js, branch: trunk, size: 5671 [annotate] [blame] [check-ins using] [diff]

The only places where BOOL is left are those where they are required by
the ABI. file: [bbf8e3f8e2] check-in: [c5ef582958] user: js, branch: trunk, size: 5311 [annotate] [blame] [check-ins using] [diff]