If we rely on vector but in a consteval context, I don't think there's an
issue (I wonder if that subtlety is discussed when examining what goes in
freestanding; I don't remember, personally) since it gets rid of the costs
for memory allocation as well as those for exception handling. It would be
cool if freestanding distinguished runtime and consteval contexts for these
tools. Unless there are costs I'm missing here (that's possible)...

Le ven. 2 févr. 2024 à 18:58, Paul M. Bendixen via SG14 <
sg14_at_[hidden]> a écrit :

> Hello all
>
> Just wanted to mention something that might be interesting for the
> February meeting.
>
> I recently saw a comment on the current state of reflection that seems to
> be moving again ( https://wg21.link/p2996 ).
> The worry was that the interface seems to rely on std::vector, and where
> it relates to strings, it uses std::string_view,
> maybe a std::span or even std::array could be used instead?
> Is this (and other parts of the reflection proposal) something we should
> consider during the feb meeting?
>
> Michael also mentioned it might be interesting to get Ben Craig on to talk
> about what's going on in freestanding?
>
> Best regards
> Paul M. Bendixen
>
> • − − •/• −/• • −/• − • •/− • • •/•/− •/− • •/• •/− • • −/•/− •/• − − •−
> •/− − •/− −/• −/• •/• − • •/• − • − • −/− • − •/− − −/− −//
> _______________________________________________
> SG14 mailing list
> SG14_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg14
>