Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Bo Persson Newsgroups: comp.lang.c++ Subject: Re: is_standard_layout vs is_pod Date: Fri, 24 Jan 2020 10:14:52 +0100 Lines: 12 Message-ID: References: <856b47d8-fdfd-4167-9c01-587b59bafe7f@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 4Ep1ejrv6ITRF+yG2nlB4gIpmr0gGuywaTir6cwz/HG4oVHOu+ Cancel-Lock: sha1:q5zMMuw8u03+r745QU51yv/tD28= User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 In-Reply-To: <856b47d8-fdfd-4167-9c01-587b59bafe7f@googlegroups.com> Content-Language: sv Xref: csiph.com comp.lang.c++:71538 On 2020-01-24 at 07:17, Daniel wrote: > Can someone explain what is the difference between is_standard_layout and is_pod, and why the latter is being deprecated in 2020? > The is_pod tests several conditions that have been separated into is_standard_layout and is_trivial. So, is_pod is no longer used by the standard library (except as the deprecated type trait). Bo Persson