[stream.types][derivation] What are "basic integral types"? LWG3696 #5240

Activity

1. jwakely commented on Jan 28, 2022

   

   jwakely

   on Jan 28, 2022

   Member

   More actions

   I think [stream.types] is trying to say "standard signed integer types", and the footnote should say "standard integer types".
2. jensmaurer commented on Jan 28, 2022

   

   jensmaurer

   on Jan 28, 2022

   Last edited by jensmaurer

   Member

   More actions

   [support.types.layout] p2 and p3 imply that ptrdiff_t and size_t can be extended integer types.
   Changing the footnote as requested would make it inconsistent with the normative rule.

   @jwakely, I think it's not editorially-obvious whether [stream.types] wants to allow extended integer types or not. It is at least conceivable to have a platform where the largest standard integer type is 32 bits, yet an extended integer type is used to represent 64-bit file sizes.

   (I'm reading the existing "basic" as possibly meaning "built-in".)

   Could you please make this an LWG issue that makes all of [support.types.layout], [stream.types], and [derivation] consistent?

   👍React with 👍2Reacted by Jonathan Wakely and A. Jiang
3. jensmaurer

   added

   lwgIssue must be reviewed by LWG.Issue must be reviewed by LWG.

   on Jan 28, 2022
4. jensmaurer commented on Jan 28, 2022

   

   jensmaurer

   on Jan 28, 2022

   Member

   More actions

   I think the footnote can be fixed editorially by simple dropping "for basic integral types", since it applies to any typedef.
5. frederick-vs-ja commented on May 8, 2022

   

   frederick-vs-ja

   on May 8, 2022

   ContributorAuthor

   More actions

   This is now LWG3696.
6. frederick-vs-ja

   changed the title [-][stream.types][derivation] What are "basic integral types"?[/-] [+][stream.types][derivation] What are "basic integral types"? LWG3696[/+] on May 8, 2022