Giving just quick answers inline ...
On 25.01.2018 23:05, Dan Haywood wrote:
When refactoring applib, I felt the need for a place, where we could put
utility classes, that we can share among the entire(!) core code base,
without having to care too much about changes without notice. Since
every other module depends on applib, except for 'unittestsupport' and I
guess 'schema', applib seemed to be the natural place for this.
This would exclude applib from access to the internal API. (Which in my
refactored version requires access to the new _Reflect and _Context
classes, and makes heavy use of _NullSafe.)
From my point of view, a technical solution could be to have the
internal API in a separate module, but share it also with applib!