Revision f312e66e32565e0b2e30e2cfe03b79ec813e78bf authored by Vassil Vassilev on 06 February 2014, 09:29:27 UTC, committed by Vassil Vassilev on 06 February 2014, 13:28:10 UTC
In the past we used that routine as sanity check whether we are reverting in the correct order. Now we have store/compare state. Moreover this is wrong because the the template specializations create a mess in the order, because the pattern is being added to the context but not the underlying declarations. This breaks the logic of the visitor as it needs to have two completely different code paths for templates and the rest of the decls only because we wanted to keep this logic. Now is a lot simpler. Remove the decl if it was in the context, without providing any sanity checks what so ever.
1 parent cb5d2c5
Computing file changes ...
