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
There are many semantic requirements of form "... type(s) model(s) some concept only if..." in specifications of standard concepts. However, as mentioned in #4054, there are also semantic requirements not of such form, and there are cases where semantic requirements are separated into different bullets (e.g. [iterator.concept.random.access]).
Should we add the "semantic requirements" element and specify semantic requirements consistently by it?
The text was updated successfully, but these errors were encountered:
There are many semantic requirements of form "... type(s) model(s) some concept only if..." in specifications of standard concepts. However, as mentioned in #4054, there are also semantic requirements not of such form, and there are cases where semantic requirements are separated into different bullets (e.g. [iterator.concept.random.access]).
Should we add the "semantic requirements" element and specify semantic requirements consistently by it?
The text was updated successfully, but these errors were encountered: