Hi,

next follows two DRAFT proposal related to Structured binding and
product types access.

Please let me know what do you think.


Structured binding: customization point issues
=============================

This paper proposes two alternative approaches to cover with two
possible issue on Structured binding P0217R1 wording: P0217R1 adds an
additional dependency of the core language on the library file <utility>
and that, to the authors knowledge, the user is unable to customize
completely bitfields members.

The first approach is to add additional wording to Structured binding
P0217R1 to cover with the core language dependency on the library file
<utility>.

The second one consists in changing the customization points of
Structured binding to something more specific and related to product
types: product_type_size and  product_type_get. These functions would be
either members or non-members found by ADL so that we remove the
dependency from the library file.

It is weird that Structured binding provides access to types that can
not be customized by the user.


Product types access
=============

This paper proposes a library interface to access the same types covered
by Structured binding SBR. This proposal name them product types The
interface includes getting the number of elements, access to the nth
element and the type of the nth element.

The wording depends on the wording of SBR.

While the last paper could be seen as a revision of P0197R0-"Default
tuple-like access", it takes a quite different approach and it is
addressed only to LEWG even if EWG could also be concerned, so I'm
wondering it it would be disturbing to use the same number.

Best,
Vicente

[SBR] Structured binding: alternative design for customization points
https://github.com/viboes/std-make/blob/master/doc/proposal/reflection/StructuredBindingRedesign.md

[PT] Product types access
https://github.com/viboes/std-make/blob/master/doc/proposal/reflection/ProductTypes.md

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/572610D8.8040004%40wanadoo.fr.

.