A previous patch made it so that ValueObjects could update themselves even in...
A previous patch made it so that ValueObjects could update themselves even in the face of an invalid execution context (which was required for the dynamic and synthetic values of const objects) It turns out, child values also need similar provisions This patch simplifies things a bit allowing ValueObject subclasses to just declare whether they can accept an invalid context at update time, and letting the update machinery in the EvaluationPoint to the rest Also, this lets ValueObjectChild proclaim that its parent chooses whether such blank-slate updates are possible llvm-svn: 237714
Loading
Please sign in to comment