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
{{ message }}
This repository has been archived by the owner on Mar 30, 2021. It is now read-only.
I was wondering how could we avoid these errors when a node from the
"from" context is passed to a constructor of a node in the
"to"context.
This came up with the Concepts patches:
E.g. https://reviews.llvm.org/D43357#inline-538221
Since GetImportedOrCreateDecl is the one which forwards the nodes as
parameters, maybe with some template metaprogramming we could enforce
that all the forwarded nodes are in the "to" context ... but it is
still not a full coverage because there are nodes with additional
setSubexpression() functions which may be called after create: https://reviews.llvm.org/D44352#inline-538212
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was wondering how could we avoid these errors when a node from the
"from" context is passed to a constructor of a node in the
"to"context.
This came up with the Concepts patches:
E.g. https://reviews.llvm.org/D43357#inline-538221
Since
GetImportedOrCreateDecl
is the one which forwards the nodes asparameters, maybe with some template metaprogramming we could enforce
that all the forwarded nodes are in the "to" context ... but it is
still not a full coverage because there are nodes with additional
setSubexpression() functions which may be called after create:
https://reviews.llvm.org/D44352#inline-538212
The text was updated successfully, but these errors were encountered: