We can't have a Matcher<T> as an out argument, because it doesn't have a 
default constructor.
  I could change the interface to return an llvm::Optional<Matcher<T>> instead, 
which doesn't require one.
  It would remove the has/get duality. The caller would always call get() and 
then check hasValue() in it.

http://llvm-reviews.chandlerc.com/D1446
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

Reply via email to