Lines Matching refs:promoted

636 promoted>> to another extension or to a core API version, then as a
637 _general_ rule, the dependency is also satisfied by the promoted extension
640 are also required or enabled by the promoted extension or core version.
641 However, in some cases an extension is promoted while making some of its
642 features optional in the promoted extension or core version.
645 dependency and the promoted version in the <<extensions, Layers &
780 Extensions, or features of an extension, may: be promoted to a new
784 When extension functionality is promoted, minor changes may: be introduced,
796 If extension functionality is promoted, there is no guarantee of direct
798 original feature to the promoted one.
806 Extensions that are promoted are listed as being promoted in their extension
807 appendices, with reference to where they were promoted to.
809 When an extension is promoted, any backwards compatibility aliases which
810 exist in the extension will *not* be promoted.
816 promoted to part of a future core version, the
818 would be promoted to etext:VK_COLOR_SPACE_SRGB_NONLINEAR.
821 The ename:VK_COLORSPACE_SRGB_NONLINEAR_KHR would not be promoted, because it
863 When an extension is promoted or deprecated by a newer feature, some or all
877 For promoted types, the aliased extension type is semantically identical to
879 The C99 headers simply `typedef` the older aliases to the promoted types.
881 For promoted command aliases, however, there are two separate entry point