Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ImmutableSetMultiMapTemplates: Don't modify the identifier of the lambda #24

Merged
merged 1 commit into from
Jan 1, 2022

Conversation

rickie
Copy link
Member

@rickie rickie commented Dec 22, 2021

When the identifier in the after template is different then in the before template, the identifier is updated. This is a side-effect which we generally do not want. Perhaps we should create a check for this in the future 😉

@rickie rickie requested a review from Stephan202 December 22, 2021 12:03
Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested commit message:

Use matching lambda parameter names in Refaster before- and after-templates

@Stephan202 Stephan202 merged commit 08e99fb into master Jan 1, 2022
@Stephan202 Stephan202 deleted the rossendrijver/minor_variable_rename_fix branch January 1, 2022 13:04
@rickie
Copy link
Member Author

rickie commented Jan 2, 2022

I have a question because I'm curious 😄 . The change in this PR is rather specific. While on the other hand, the suggested commit message is a little more high-level compared to the specific change. What is the reason to (e.g.) not mention the template in the message?

@Stephan202
Copy link
Member

I assumed (but should have asked) that this change resolves it for all such templates. For me the fact that only one template was impacted is immaterial.

@Stephan202 Stephan202 added this to the 0.1.0 milestone Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants