Make self receiver and start_fn members available as official fields
#250
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anelson
approved these changes
Mar 5, 2025
Veetaha
deleted the
feat/expose-receiver-and-start-fn-members-as-builder-fields
branch
10 tasks
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is according to my design decision here: #225 (comment).
Now
bongenerates stable names for some native private fields of the builder that are documented and accessible tobonmacro users:self_receiver- stores theselfvalue of the method (for builders generated from a method){member_name}- stores the value of the member annotated with#[builder(start_fn)]. These members are initialized when the builder is created.These native private builder fields can be freely accessed in custom setters/getters or generally within the same module scope.