boost/stl_interfaces
2
0
Fork 0
mirror of https://github.com/boostorg/stl_interfaces.git synced 2026-01-19 04:42:12 +00:00
Code Issues Projects Releases Wiki Activity

Document why view_interface does not define nested types.

Browse Source 
Fixes #7.
This commit is contained in:
Zach Laine
2019-12-17 22:59:33 -06:00
parent 086773847b
commit 7c4a420f8d
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/rationale.qbk
View File

@@ -51,6 +51,18 @@ typedefs in the `view` concept. For _cont_iface_, it was deemed ridiculous to
create a template whose purpose is to reduce code size, which takes 14
template parameters.
[heading _cont_iface_ Does not Deduce Nested Types Like `iterator`]
_cont_iface_ could deduce some of the nested types required for a standard
sequence container. For instance, `iterator` can be deduced as
`decltype(*begin())`. However, a type `D` derived from _cont_iface_ may need
to use some of these nested types _emdash_ like `iterator` _emdash_ in its
interface or implementation. If this is the case, those nested types are not
available early enough in the parse to be used in `D`, if they come from
deductions in _cont_iface_. This leaves the user in the awkward position of
defining the same nested type with a different name that can be used within
`D`. It seems better to leave these types for the user to define.
[heading _cont_iface_ Does not Support Associative or Unordered Associative Containers]
That's right. Associative containers have an interface that assumes that they