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
Would \prop_(g)put_if_not_in:Nnn be easier to understand than the current \prop_(g)put_if_new:Nnn?
We have \<type>_if_in:Nn(TF) and all other occurrences of "new" in l3kernel function names are verb-like: new, new_conditional, (g)clear_new, (g)zero_new.
The text was updated successfully, but these errors were encountered:
My initial reaction would be yes, it seems easier to understand as I wouldn't perceive a "key" as an object and it also fits better with \prop_if_in:NnTF.
Would
\prop_(g)put_if_not_in:Nnn
be easier to understand than the current\prop_(g)put_if_new:Nnn
?We have
\<type>_if_in:Nn(TF)
and all other occurrences of "new" in l3kernel function names are verb-like:new
,new_conditional
,(g)clear_new
,(g)zero_new
.The text was updated successfully, but these errors were encountered: