Problem

There are some edge cases with SectionNode claiming related to Functions and EffectSections. Currently, functions can always be used with sections, even if no parameter claims the section. This results in random unparsed code. EffectSections also do not properly work with ExpressionSections. The "sectionNode" of the SectionContext is always null, meaning there is nothing to claim (even if one is present). This can result in unclaimed/unparsed code.

Solution

For Functions

I simply added a check similar to the one performed below for Statement that ensures the Section has been claimed. I tweaked the error message to better fit functions. It does not currently attempt to try parsing as an EffectSection or Statement. This is partly due to the logging setup, and I believe that syntax conflicting with function calls is not currently supported anyways.

For EffectSections

I added a new EffectSection#parse override that supports specifying whether the sectionNode parameter can be claimed by the parsed EffectSection. This uses an internal ParserInstance context for passing this information around.

Testing Completed

A test for the Function edge case was added.

Supporting Information

Completes: none
Related: none