[MacPorts] #63364: mu @1.6.3: error: no matching constructor for initialization of 'value_type' (aka 'pair<const std::__1::basic_string<char>, Container>')

[MacPorts]

#63364: mu @1.6.3: error: no matching constructor for initialization of
'value_type' (aka 'pair<const std::__1::basic_string<char>, Container>')
-------------------------+--------------------------------
  Reporter:  ryandesign  |      Owner:  ra1nb0w
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.7.1
Resolution:  fixed       |   Keywords:  yosemite elcapitan
      Port:  mu          |
-------------------------+--------------------------------

Comment (by kencu):

 c++ feature support in compilers is more of a curve of implementation
 rather than a square wave:

 https://clang.llvm.org/cxx_status.html

 MacPorts sets the bar for standard support at a reasonable level. If set
 too high, many ports that build fine with the system clang would
 needlessly call in a macports-clang for the build.

 Some features of c++17 and c++20 are still unimplemented by clang.

 and Apple's clang versions are of course related to but not directly
 translatable to the oss clang versions...

-- 
Ticket URL: <https://trac.macports.org/ticket/63364#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS