| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Clang issues warnings at build time based on the SERD_NONNULL annotations,
which is a much better approach in general. However, it does not cover cases
where the API is being used with another compiler, or without a compiler that
can statically check things at all (such as Python or other dynamic language
bindings).
In those situations, getting a clear assertion message is a lot less confusing
than a random crash somewhere in serd, and it makes it clear that the bug is in
the caller, so I think it's worth the tedious verbosity.
|
|
|
|
|
|
|
|
|
|
|
|
Using inconsistent defines like this that affect the standard library
implementation can cause issues. So, doing this consistently for the whole
library is a better approach, although it unfortunately makes the code more
difficult to compile manually.
|
|
More const never hurts in general, but in particular this allows the compiler
to make better nullability deductions, which reduces the amount of manual
nullability casting required.
|
|
This causes build issues when targeting older versions of MacOS. That could be
fixed, but I don't have the ability to reproduce it at the moment, and it's a
problem in the build system check code which is about to be entirely replaced
anyway.
Since, as far as I know, this does not actually add aligned allocation support
to any real system (they all support one of the other methods), just remove it
for now.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
