feat: enable pp.fieldNotation.generalized
globally
#3744
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sets the default value to
pp.fieldNotation.generalized
totrue
. Updates tests, and fixes some minor flaws in the implementation of the generalized field notation pretty printer.Now generalized field notation won't be used for any function that has a
motive
argument. This is intended to prevent recursors from pretty printing using it as (1) recursors are more like control flow structures than actual functions and (2) generalized field notation tends to cause elaboration problems for recursors.Note: be sure functions that have an
@[app_unexpander]
use@[pp_nodot]
if applicable. For example,List.toArray
needs@[pp_nodot]
to ensure the unexpander prints it using#[...]
notation.