summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Analysis/LazyCallGraph.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2014-03-03 10:28:38 +0000
committerChandler Carruth <chandlerc@gmail.com>2014-03-03 10:28:38 +0000
commitd5346dcf3e34877030bcb5fe82ee79fca8f7af0f (patch)
tree2c6b915e3b109b4a445d19c7a47bcc639bf43bbf /llvm/lib/Analysis/LazyCallGraph.cpp
parentf93725459a0b2e8d7b056a545d245d029d93c6cd (diff)
downloadbcm5719-llvm-d5346dcf3e34877030bcb5fe82ee79fca8f7af0f.tar.gz
bcm5719-llvm-d5346dcf3e34877030bcb5fe82ee79fca8f7af0f.zip
[C++11] Add an iterator_range class template. This is modeled on the
proposed std::iterator_pair which was in committee suggested to move toward std::iterator_range. There isn't a formal paper yet, but there seems little disagreement within the committee at this point so it seems fine to provide our own version in the llvm namespace so we can easily build range adaptors for the numerous iterators in LLVM's interfaces. Note that I'm not really comfortable advocating a crazed range-based migration just yet. The range stuff is still in a great deal of flux in C++ and the committee hasn't entirely made up its mind (afaict) about how it will work. So I'm mostly trying to provide the minimal functionality needed to make writing easy and convenient range adaptors for range based for loops easy and convenient. ;] Subsequent patches will use this across the fundamental IR types, where there are iterator views. llvm-svn: 202686
Diffstat (limited to 'llvm/lib/Analysis/LazyCallGraph.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud