Lines Matching full:conflict
101 * **Namespaces**: Unlike in some languages, modules do not imply any notion of namespaces. Thus, a struct declared in one module will still conflict with a struct of the same name declared in a different module, just as they would if declared in two different headers. This aspect is important for backward compatibility, because (for example) the mangled names of entities in software libraries must not change when introducing modules.
238 ``conflict`` ``framework`` ``requires``
296 *conflict-declaration*
598 Conflict declarations
600 A *conflict-declaration* describes a case where the presence of two different modules in the same translation unit is likely to cause a problem. For example, two modules may provide similar-but-incompatible functionality.
604 *conflict-declaration*:
605 ``conflict`` *module-id* ',' *string-literal*
607 The *module-id* of the *conflict-declaration* specifies the module with which the enclosing module conflicts. The specified module shall not have been imported in the translation unit when the enclosing module is imported.
609 The *string-literal* provides a message to be provided as part of the compiler diagnostic when two modules conflict.
613 Clang emits a warning (under the control of ``-Wmodule-conflict``)
614 when a module conflict is discovered.
623 conflict B, "we just don't like B"
