David Feltell

WIP

`BatchElementError` type for callback-based batch methods

1

# What Add a `BatchElementError` class to be used in error callbacks for batch-first API methods. # Why Our batch-first design means that errors that affect only a single element...

# What Following on from #557, implement the C API for `BatchElementError` # Why This is a requirement for a functional C host. # Notes Design sketch ```c /** *...

C API for `EntityReference`

2

# What Following on from #549, we must implement the C API for the `EntityReference` class and its related `Manager` member functions. # Why This is a requirement for a...

Closes #557. Add a simple `BatchElementError` aggregate class, initially containing just an error code and string message. The error code is a strongly typed enumeration, currently only supporting a fallback...

# What Investigate whether `enum class` (rather than old-style `enum`) can/should be used for `Context::Access` and `Context::Retention`. If old-stye `enum`s are chosen for `Context`, then decide whether `BatchElementError::ErrorCode` should be...

Update tests and docs to use `EntityReference` object workflows. Since most of the implementation is still in weakly-typed Python, there isn't much in the way of core code changes. Though...

# What Either * Add support in the C++ implementation of `isEntityReferenceString` for a prefix-based default via the `kField_EntityReferencesMatchPrefix` property of the manager's `info()` dictionary; or * Remove references to...

More use of `std::string_view` for read-only or copy-only strings

1

# What Swap out usages of `const std::string&`/`const Str&` for `std::string_view` wherever it makes sense, i.e. where we can't be certain in what form a string will be passed (e.g....

# What Following on from #501, implement the C API for `managerInterface`.