This is a big issue, with the purpose of addressing database bloat in V8 indexes due to the V8_EXPORT macro. In different translation units, this macro expands differently, resulting in the same classes, or class templates, "looking" different to multiplier's AST/code-based deduplication logic. As a result, there can be two or more copies of many classes stored in the database. This has knock-on effects for the methods, especially method templates.
This is a big issue, with the purpose of addressing database bloat in V8 indexes due to the
V8_EXPORTmacro. In different translation units, this macro expands differently, resulting in the same classes, or class templates, "looking" different to multiplier's AST/code-based deduplication logic. As a result, there can be two or more copies of many classes stored in the database. This has knock-on effects for the methods, especially method templates.