[ elab ] Support easy collection of information during TTImp
traverse
#3193
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.
Description
Current applicative traversals introduced at #3130 can be used for analysis of an expression, e.g. for collecting some data. But since currently the only way to analyse expression is to analyse the result of
pure
, usedApplicative
must contain at least on level of expressions, disallowing simple stuff likeConst
functor for applicative traversals for collecting the data.But once we pass the original expression along with the current data to the user function, we gain the ability to traverse the data with simple applicatives, like
Const
. You can see an example of such collecting traversal in the newly added test.This is a backward-compatible change in terms of main existing functions
mapATTImp
andmapMTTImp
. However, intermediate functions formapM<WhateveElse>
changed their signatures to support usingmapATTImp'
internally.Should this change go in the CHANGELOG?
implementation, I have updated
CHANGELOG_NEXT.md
(and potentially alsoCONTRIBUTORS.md
).