For readability, maintenance and organization, it’d be neat if we could next a context definition inside another context. a nested context would then only be useable inside the enclosing context. Thus we could have:
contexts:
general_context_1:
- nested_contexts:
specific_context_a_only_really used_inisde_context_1:
#...
specific_context_a_only_really used_inisde_context_1:
#...
#more specific contexts
general_context_2
- nested_contexts:
specific_context_c_only_really used_inisde_context_2:
#...
specific_context_d_only_really used_inisde_context_2:
#...
#more specific contexts
instead of
contexts:
general_context_1:
#...
specific_context_a_only_really used_inisde_context_1:
#...
specific_context_a_only_really used_inisde_context_1:
#...
#more 1-specific contexts
general_context_2
#...
specific_context_c_only_really used_inisde_context_2:
#...
specific_context_d_only_really used_inisde_context_2:
#...
#more 2-specific contexts
In the proposed way, it’s crystal clear where a context is just a specialised state in a more general construct, and I suspect many standard syntaxes could be made more readable for new developers that read/study them.