-
Notifications
You must be signed in to change notification settings - Fork 2
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
Proposal implementation #5
Open
arepnikov
wants to merge
25
commits into
eventide-project:master
Choose a base branch
from
arepnikov:proposal-implementation
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Proposal implementation #5
arepnikov
wants to merge
25
commits into
eventide-project:master
from
arepnikov:proposal-implementation
Conversation
This file contains 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
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
test/automated/reflection/parameters/method_is_not_implemented.rb
Outdated
Show resolved
Hide resolved
ntl
reviewed
Aug 28, 2024
test/automated/reflection/parameters/method_is_not_implemented.rb
Outdated
Show resolved
Hide resolved
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
ntl
reviewed
Aug 28, 2024
test/automated/reflection/variant_actuator/method_is_not_implemented.rb
Outdated
Show resolved
Hide resolved
target_accessor should be implemented in terms of target_method, not the other way around. def target_accessor? rather than alias, since it's a distinct member of Reflection's protocol
we can replace `send` with `public_send`, since before was called `respond_to?` (without any optional arguments), which means that respond_to? returned true only for existing public methods.
ntl
reviewed
Sep 16, 2024
ntl
reviewed
Sep 16, 2024
ntl
reviewed
Sep 16, 2024
ntl
reviewed
Sep 16, 2024
ntl
reviewed
Sep 16, 2024
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.
Reflect Library Improvements Proposal
Background
In Eventide's libraries, Reflect has 6 use cases, but 4 of them do not utilize it in the designed way. Instead of making a use of the reflection's actuator, the constant is pulled from the reflection.
The actuator is designed to pass the subject into the method being invoked. The subject can also be overridden, but either way, exactly one argument is always supplied to the protocol method:
However, the actuator doesn't support methods with zero arity or methods with arity greater than one. Due to this limitation, the constant is often pulled from the reflection, bypassing the actuator.
If the reflection's actuator were to support invoking protocol methods with any arity, then most use cases of the reflect library would be able to use the actuator and avoid disencapsulating the reflection's target constant.
Reflection's Actuator
Example: Method Without Arguments
Current Approach (Workaround)
Proposed Approach
Example: Method With More Than One Argument
Current Way Around
Proposed Change
Reflection's Variant Actuator
Support for methods with any parameter signature is proposed. This necessitates a way to invoke the reflection's actuator so that it supplies the reflection's subject into the protocol method.
To address this, the introduction of a variant actuator method
.!()
is proposed. The variant actuator will pass the subject into the invoked method as the first positional argument, but will otherwise behave the same as the primary actuator:Additional Changes
Target Method Predicate
Arity Method
Parameters Method