<HTML>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<TITLE>
    CWG Issue 1881</TITLE>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<STYLE TYPE="text/css">
  INS { text-decoration:none; font-weight:bold; background-color:#A0FFA0 }
  .INS { text-decoration:none; background-color:#D0FFD0 }
  DEL { text-decoration:line-through; background-color:#FFA0A0 }
  .DEL { text-decoration:line-through; background-color: #FFD0D0 }
  @media (prefers-color-scheme: dark) {
    HTML { background-color:#202020; color:#f0f0f0; }
    A { color:#5bc0ff; }
    A:visited { color:#c6a8ff; }
    A:hover, a:focus { color:#afd7ff; }
    INS { background-color:#033a16; color:#aff5b4; }
    .INS { background-color: #033a16; }
    DEL { background-color:#67060c; color:#ffdcd7; }
    .DEL { background-color:#67060c; }
  }
  SPAN.cmnt { font-family:Times; font-style:italic }
</STYLE>
</HEAD>
<BODY>
<P><EM>This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21
  Core Issues List revision 118b.
  See http://www.open-std.org/jtc1/sc22/wg21/ for the official
  list.</EM></P>
<P>2025-09-28</P>
<HR>
<A NAME="1881"></A><H4>1881.
  
Standard-layout classes and unnamed bit-fields
</H4>
<B>Section: </B>Clause 11&#160; [<A href="https://wg21.link/class">class</A>]
 &#160;&#160;&#160;

 <B>Status: </B>CD4
 &#160;&#160;&#160;

 <B>Submitter: </B>Dinka Ranns
 &#160;&#160;&#160;

 <B>Date: </B>2014-02-25<BR>


<P>[Moved to DR at the November, 2014 meeting.]</P>



<P>According to 11.4.10 [<A href="https://wg21.link/class.bit#2">class.bit</A>] paragraph 2,</P>

<BLOCKQUOTE>

Unnamed bit-fields are not members and cannot be initialized.

</BLOCKQUOTE>

<P>However, the rules defining standard-layout classes in
Clause 11 [<A href="https://wg21.link/class#7">class</A>] paragraph 7 do not account for the fact that
a class containing an unnamed bit-field has associated storage.</P>

<P>See also <A HREF="1813.html">issue 1813</A> for a related
question about standard-layout classes.</P>

<P><B>Proposed resolution (June, 2014):</B></P>

<P>This issue is resolved by the resolution of
<A HREF="1813.html">issue 1813</A>.</P>

<BR><BR>
</BODY>
</HTML>
