> Most often it is not necessary, and not wanted, to enforce a and b having the same type.
That really depends on what you're trying to do. Presenting these two different declarations as somehow equivalent is very misleading and I'm glad that the author didn't do that.
They are not presented as equivalent, but as a choice.
The author's failing was in presenting neither of them until long after they were due, and presenting thoroughly inferior alternatives in the meantime.
The right place to put a concept name, in production code, is in place of "typename" in a template definition, or even better in place of "T" in the function argument declaration. That is, instead of
say or according as whether you want to enforce a and b to have the same type (which is another omission).Most often it is not necessary, and not wanted, to enforce a and b having the same type.