One thing I forgot to mention, this also applies to the deduction done for partial specializations, temp.deduct.type appliesSent from my Samsung Galaxy smartphone.
-------- Original message --------From: Will Hawkins via Std-Discussion <std-discussion_at_[hidden]> Date: 8/4/19 23:27 (GMT-05:00) To: std-discussion_at_[hidden] Cc: Will Hawkins <hawkinsw_at_[hidden]> Subject: [std-discussion] Temp.deduct.type applicability Hello experts!I'm sorry for such a basic question, but I'm trying to see the forest again after studying the trees of section temp.fct.spec. In particular, paragraph 4 of temp.deduct.call talks about type deduction generally. Until that point, the rules cover the "preparation" P and A for actual deduction. The introduction to temp.deduct also refers to deduction with being explicit about how it is accomplished. Contrast this with the explicit reference to the rules for deduction in temp.deduct.funcaddr, e.g..It seems logical that those sections assume that the reader can connect the dots and I believe that is the proper reading. In other words, anywhere in temp.fct.spec that talks about type deduction (after the conditioning of P and A described therein), the deduction is assumed to follow the rules of temp.deduct.type. I was hoping to have confirmation of that, or correction in the (likely) case that I am wrong!Thank you for your help!Will