P1393 A General Property Customization Mechanism #185
Forward P1393 to LWG for a to-be-formed Executors TS.
Forward P1393 to LWG for C++Next.
Should be seen by LWG, no sooner than Belfast. Other Executors-related pieces will go to LEWG starting in Cologne for the C++23/C++Next cycle.
EWG telecon on May 21st 2020:
Properties are part of executors and are therefore one of the top items in the Bold Plan in P0592. Our main goal was to look at what's nominally a Library proposal and understand what, if anything, Language should do. In other words: don't design in isolation (neither Library nor Language).
One action item came out of this: Daisy to start a discussion with Daveed, Eric, Andrew, and Ville, regarding reflection + properties.
We didn't identify major parts of the proposal which should be done through Language facilities. We did, however, discuss a few places where better Language support might simplify properties / executors, and change what the Library parts look like:
None are blocking properties at the moment.
We took one straw poll, not as a binding decision but rather to understand what those present for the discussion thought.
Do we understand properties and think that specifying them purely in library is the right approach?
We'll revisit properties when EWG is next able to take binding decisions.
Poll: We understand properties and think that specifying them purely in library is the right approach.
Poll outcome: ❌ no consensus, participants do not understand properties, and might want to specify executors' customizations mechanism as a language feature.