[analyzer] Add range constructor to CallDescriptionMap

[gamesh411]

Summary

CallDescriptionMap benefits from a range constructor when the
CallDescription and mapped type pairs cannot be constructed at once, but
are built incrementally.

[steakhal]

LGTM

clang/unittests/StaticAnalyzer/CallDescriptionTest.cpp

24–28 ↗

(On Diff #395097)

I'm not even sure we need this assertion though.

38 ↗

(On Diff #395097)

Maybe the ResultMap should also follow this and declare the ctor overload.

[gamesh411]

Remove static asserts as it only makes the tests more brittle

clang/include/clang/StaticAnalyzer/Core/PathSensitive/CallDescription.h

template <typename T> class CallDescriptionMap {
   // descriptions (eg., the ones for C functions that just match the name).
   std::vector<std::pair<CallDescription, T>> LinearMap;
 
 public:
   CallDescriptionMap(
       std::initializer_list<std::pair<CallDescription, T>> &&List)
       : LinearMap(List) {}
 
+  template <typename InputIt>
+  CallDescriptionMap(InputIt First, InputIt Last) : LinearMap(First, Last) {}
+
   ~CallDescriptionMap() = default;
 
   // These maps are usually stored once per checker, so let's make sure
   // we don't do redundant copies.
   CallDescriptionMap(const CallDescriptionMap &) = delete;
   CallDescriptionMap &operator=(const CallDescription &) = delete;
 
   CallDescriptionMap(CallDescriptionMap &&) = default;