LWG3515 [stacktrace.basic.nonmem]: operator<< should be less templatized

[jwakely]

LWG would like LEWG to review LWG 3515 and decide whether the proposed resolution is the right direction.

This is a new C++23 feature, so it would be good to get this resolved in time for C++23.

[brycelelbach]

2022-09-27 Library Evolution Telecon

LWG3515: [stacktrace.basic.nonmem]: operator<< should be less templatized

2022-09-27 Library Evolution Telecon Minutes

Chair: Bryce Adelstein Lelbach

Minute Taker: Steve Downey

Start: 2022-09-27 12:04 Eastern

POLL: Send the proposed resolution for LWG3515 ([stacktrace.basic.nonmem]: operator<< should be less templatized) to Library for C++23 classified as B2 - Improvement, to be confirmed with a Library Evolution electronic poll.

Strongly Favor	Weakly Favor	Neutral	Weakly Against	Strongly Against
7	6	1	0	0

Attendance: 20

Outcome: Consensus in favor.

End: 12:15

Summary

This issue points out that it's unnecessary for stacktrace's output streaming operator to be templated on the stream's character and character traits type, because stacktrace always passes a string to the stream, requiring that the character type be char and the character traits type be char_traits<char>. The proposed resolution is to detemplatize these operators.

We discussed whether we want stacktrace to support wide strings. Most felt that this could be explored in the future and shouldn't stop us from making this simplification now. We could always add more overloads in the future.

Next Steps

Take an electronic poll to send the proposed resolution for LWG3515 ([stacktrace.basic.nonmem]: operator<< should be less templatized) to Library for C++23 classified as B2 - Improvement, to be confirmed with a Library Evolution electronic poll.