[PATCH] Add -Wrange-loop-analysis to warn when a range-based for-loop is creating a copy.

[David Blaikie]

In http://reviews.llvm.org/D4169#68650, @dblaikie wrote:

> You could probably be a bit narrower than POD types - probably just
>  types with trivial copy constructors. But for now "all POD types"
>  shouldn't have any false positives, only false negatives - so perhaps
>  leave it that way with a FIXME Describing a narrower check for small
>  types (small to be defined/discovered) with trivial copy construction.


Have you addressed these suggestions?

I don't recall where this was all left, exactly.


http://reviews.llvm.org/D4169

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/