You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The generic storage used for e.g. Attribute values was initially designed to store arbitrary datatypes, hence the name Variadic was chosen.
During developement it became pretty obvious that a restriction to a finite, predefined set of datatypes is the more sensible way. Since boost/mpark/stdvariants do exactly that, they have been used all along.
I propose to rename the auxiliary class Variadic to Variant to reflect this decision.
The text was updated successfully, but these errors were encountered:
The generic storage used for e.g. Attribute values was initially designed to store arbitrary datatypes, hence the name
Variadic
was chosen.During developement it became pretty obvious that a restriction to a finite, predefined set of datatypes is the more sensible way. Since
boost
/mpark
/std
variant
s do exactly that, they have been used all along.I propose to rename the auxiliary class Variadic to
Variant
to reflect this decision.The text was updated successfully, but these errors were encountered: