Ryo Onodera

> Maybe, I'll introduce `EpochGroup` trait and `EpochGroup::global()` or something at `crossbeam-epoch` and pass the type parameter way up to the application code via `crossbeam-deque` and `rayon`. I made this...

fyi, the original approch's newer api would look like this: ```rust use crossbeam_deque::{CustomCollector, Collector, LocalHandle}; static MY_COLLECTOR: Lazy = Lazy::new(Collector::new); // note that, maybe i need to provide macro_rule! for...

@adamreichold thanks for chiming in. :) loves collective wisdom. your idea sounds doable. so, i created https://github.com/solana-labs/solana/pull/26555

sorry for begging. but i want this feature really and waited almost a year. :)

@brooksprumo sorry for late review... i added some improvement suggestions. let's make status cache robust together. :)

I think the general direction is so good. Discussed elsewhere, i think this pr can further be smaller? could you rework? (sorry for wasted efforts...)

> Alternative: store the Bank's `accounts_data_len` in the snapshot, and then that'll be used when loading from the snapshot. @brooksprumo well, if `accounts_data_len` can be computed at the startup time,...

i know. i'm very late to comment at this moment... could you polish up your (already well-written) issue description a bit, regarding the following questions? > Make transactions fail if...

thanks for more details. > Is calculating at startup preferred in your opinion? yeah, but not strong opinion. the role of accounts_data_len would be like the snapshot hash. ideally, this...

heh, this is a fairly good and old issue. :) fyi, I'm creating a pr for this: #959