You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: