New issue from Jakub: meta::access_context should be a consteval-only type

Author: jwakely

xml/issue4422.xml

@@ -0,0 +1,41 @@
+<?xml version='1.0' encoding='utf-8' standalone='no'?>
+<!DOCTYPE issue SYSTEM "lwg-issue.dtd">
+
+<issue num="4422" status="New">
+<title>`meta::access_context` should be a consteval-only type</title>
+<section><sref ref="[meta.reflection.access.context]"/></section>
+<submitter>Jakub Jelinek</submitter>
+<date>20 Oct 2025</date>
+<priority>99</priority>
+
+<discussion>
+<p>
+The `meta::access_context` type is expected to contain some `meta::info`
+objects, which would make it a consteval-only type. But we don't actually
+specify any members, so nothing in the current specification says you can't
+persist one until runtime.
+</p>
+</discussion>
+
+<resolution>
+<p>
+This wording is relative to <paper num="N5014"/>.
+</p>
+
+<ol>
+
+<li><p>Modify <sref ref="[meta.reflection.access.context]"/> as indicated:</p>
+
+<blockquote>
+<p>-1-
+The access_context class is a non-aggregate<ins>, consteval-only</ins> type
+that represents a namespace, class, or function from which queries pertaining
+to access rules may be performed, as well as the designating class
+(<sref ref="[class.access.base]"/>), if any.
+</p>
+</blockquote>
+</li>
+</ol>
+</resolution>
+
+</issue>