Template talk:dcl rev begin

I think it would be useful if we could link to specific overloads, I was thinking of adding a {{tt| {{#if:{{{num|}}}|id="dcl_{{{num|}}}" }} attribute to the {{tt|tbody}} tag. Example: (see first and second overloads). {{dcl begin}} {{dcl header | numeric}}  (1) {{dcl|until=c++20|1= template< class InputIt, class T > T accumulate( InputIt first, InputIt last, T init ); }} {{dcl|since=c++20|1= template< class InputIt, class T > constexpr T accumulate( InputIt first, InputIt last, T init ); }} {{dcl rev end}}  (2) {{dcl|until=c++20|1= template< class InputIt, class T, class BinaryOperation > T accumulate( InputIt first, InputIt last, T init,             BinaryOperation op ); }} {{dcl|since=c++20|1= template< class InputIt, class T, class BinaryOperation > constexpr T accumulate( InputIt first, InputIt last, T init,                       BinaryOperation op ); }} {{dcl rev end}} {{dcl end}}

Any objections? Would need to make the analogous change to the {{tt|dcl}} template for the {{tt|tr}} tag also --Ybab321 (talk) 03:28, 16 April 2020 (PDT)


 * A row (group) with {{tt| id= "dcl_N"}} would be unique within the {{tt| {{dcl begin}}--{{dcl end}} }}, but not necessarily so within the page. Maybe an extra qualifier should be prepended, e.g. the ID of the {{tt| {{dcl begin}}--{{dcl end}} }} that contains the row (group).
 * "dcl_N" is quite meaningless. I think an overload name would be more useful: instead of (or in addition to) the {{tt|num}} parameter, a {{tt|name}} could be provided. (Careful naming would also solve problem #1.)
 * — Radix (talk) 17:10, 17 April 2020 (PDT)