We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Whenever a nested delegate is used, it is required to find the method reference by going to the previous ldsfldn (load method ref pointer)
If you have a non-nested delegate right after this one may take the nested ones invoke instead of its own.
Solution: Never use the same reference more than once. If no ldsfldn is found then the appointed method name should be used instead.
Note: Having more than one delegate nested in each other has not been tested: Ex:
DelegateA a => { DelegateB b => { . DelegateC c => {}; . c(); . } . b(); }; A();
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Whenever a nested delegate is used, it is required to find the method reference by going to the previous ldsfldn (load method ref pointer)
If you have a non-nested delegate right after this one may take the nested ones invoke instead of its own.
Solution: Never use the same reference more than once. If no ldsfldn is found then the appointed method name should be used instead.
Note: Having more than one delegate nested in each other has not been tested:
Ex:
DelegateA a => {
DelegateB b => {
. DelegateC c => {};
. c();
. }
. b();
};
A();
The text was updated successfully, but these errors were encountered: