Currently, the BlockIndex and OffloadDeepcopy pipelines rely on a naming convention to map fields to their corresponding pointers, and this is enforced by requiring a full-parse of the associated dependency tree. This can be problematic if this dependency tree is split across multiple projects let alone libraries. Instead, a user-configurable naming convention can be enforced without requiring a full-parse, especially if backed up by compile-time warnings for unparsed type-definitions.
Currently, the
BlockIndexandOffloadDeepcopypipelines rely on a naming convention to map fields to their corresponding pointers, and this is enforced by requiring a full-parse of the associated dependency tree. This can be problematic if this dependency tree is split across multiple projects let alone libraries. Instead, a user-configurable naming convention can be enforced without requiring a full-parse, especially if backed up by compile-time warnings for unparsed type-definitions.