GLSL_EXT_nontemporal_keyword: Behave strictly when passing to functions

extensions/ext/GLSL_EXT_nontemporal_keyword.txt

@@ -106,11 +106,10 @@ Modifications to the OpenGL Shading Language Specification, Version 4.60
       to functions whose formal parameters lack such qualifiers. (See
       “Function Definitions” for more detail on function calling.) It is legal
       to have any additional memory qualifiers on a formal parameter, but only
-      restrict or nontemporal can be taken away from an opaque-type calling
-      argument, by a formal parameter that lacks the restrict or nontemporal
-      qualifier respectively. For non-opaque argument types, where the values
-      operated on by the called function are copied-in/copied-out,
-      memory qualifiers are not required to match.
+      restrict can be taken away from an opaque-type calling argument, by a
+      formal parameter that lacks the restrict qualifier. For non-opaque
+      argument types, where the values operated on by the called function are
+      copied-in/copied-out, memory qualifiers are not required to match.
 
     Modify Section 8.11. Memory Qualifiers
 
@@ -148,15 +147,21 @@ Modifications to the OpenGL Shading Language Specification, Version 4.60
 
       NONTEMPORAL
 
-    after the line WRITEONLY
+    after the line "WRITEONLY"
 
 Issues
 
     (1) Should implicit removal of the keyword during function call
         be allowed (as-per the `restrict` keyword) or forbidden (as-per
         the `volatile` and `coherent` keywords)?
+
+        Feedback recieved was that behaving like `restrict` would be more
+        appropriate.
 
 Revision History
 
     Revision 1
     - Initial revision.
+    Revision 2
+    - Behaviour of `nontemporal` being passed to a function declared without it
+      is now an error.