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
Currently, we cache decls after we successfully import them. However, if we fail to import a decl, we should (but currently do not) cache them too. I suspect that this will be a big performance improvement for the compiler because currently, we can't import complex templates or dependent types, which are very expensive to traverse.
This will require fixing a few visitors along the way.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: e6fd025c695731ad4c62c7d1b91945d7
Issue Description:
Currently, we cache decls after we successfully import them. However, if we fail to import a decl, we should (but currently do not) cache them too. I suspect that this will be a big performance improvement for the compiler because currently, we can't import complex templates or dependent types, which are very expensive to traverse.
This will require fixing a few visitors along the way.
The text was updated successfully, but these errors were encountered: