-
Notifications
You must be signed in to change notification settings - Fork 269
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
refactor: load transaction accounts #2442
Conversation
748ddc0
to
829368a
Compare
|
||
account | ||
}; | ||
accumulate_and_check_loaded_account_data_size( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part looks a bit dangerous to me and could be consensus breaking if there is a slight difference in which accounts count towards the loaded_accounts_bytes
limit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed that it's a sensitive part of the code that needs extra eyes. This PR allows the instructions sysvar to hit this function call now but I have set the loaded size for that account to 0 so there should be no consensus change here.
@2501babe this changes some things in account loading, which we'll want to take into account for the SIMD83 changes. |
Any other feedback or concerns here? This refactor is not too important so I don't mind abandoning it but I think it's safe and makes things a bit easier to read. |
* refactor: load transaction accounts * feedback * fix account found * fix clippy
Problem
load_transaction_accounts
does an unnecessary clone for the fee payer account and has an unnecessary additional level of nesting for the instructions sysvar.Summary of Changes
load_transaction_accounts
to first handle the fee payer account without cloningFixes #