Meta Issue for Future Parser Changes

We are not adding anything to #2205. This is for changes after #2205 is merge.

We need to have a grasp on the parser as a whole. For each requested new parser change we need:

• a minimal example of the desired behavior
• can it be done with current parser
• If it can be, it is documented

Issues already slated for addition in parser rewrite are not included in the list.

In-Progress Rewrite

• #2205

Preparation for Future Additions

• #2835

Issues

• #2771
  • have example - yes
  • can be done now - yes
  • documented - No
  • status - tbd
• #2783
  • have example - yes
  • can be done now - no
  • documented - No
  • status - tbd
• #2676
  • have example - yes
  • can be done now - yes
  • documented - Yes, but could be better
  • status - tbd
• #2768
  • have example - yes
  • can be done now - technically yes, but really no
  • documented - ?
  • status - tbd
  • Related:
    • #2433
• #1279
  • have example - ?
  • can be done now - ?
  • documented - ?
  • status - tbd
• #928
  • have example - ?
  • can be done now - ?
  • documented - ?
  • status - tbd

Start by reviewing the in-progress parser rewrite in #2205, the preparation work in #2835, and the linked parser issues listed here. For each future parser change, establish a minimal desired-behavior example, determine whether the current parser supports it, and record whether that behavior is documented.