| Make beyondBoundsItemCount public in LazyRow and LazyColumn “ ) nmuloC/woRyzaL ni pu ti gninepo fo ytilibissop eht gniyduts er'ew dna (ti rof esac esu niam eht si hcihw) regaP ni pu ti gninepo ll'ew esuaceb etelpmoc erutaef eht dekram ev'I .sIPA lanretni tsiLyzaL eht ni llits si erutaef eht ,iH |
“ ) yletelpmoc cigol eht gnignahc htiw yalp ot yrt ot sresu rof ipa latnemirepxe elpmis a detaerc ydaerla eW .elbarugifnoc cigol siht ekam osla dna tluafed yb smeti erom hcteferp ot cigol siht gnikaewt gniredisnoc era ew dna llorcs fo noitcerid eht ni meti artxe eno hcteferp ylno ew won thgiR .eldi si daerht niam eht nehw smeti artxe gnirusaem dna gnisopmoc fo msinahcem ruo si hcteferP .smeti tnecajda gnihcteferp yb devlos eb nac sesac esu eht fo tsom raf os raeh ew tahw morFhttps://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/lazy/LazyListPrefetchStrategy.kt ), but we are still working on making this api even easier to use. Basically what I mean is that the requested use case will be solvable by still only composing items which are needed as visible during the main measure pass, and then we scheduled prefetch for a few extra items on the sides. It will make sure such item are composed before users scroll to them, but it will not block the main thread improving the performance.
After we support that the only reason to still use apis like beyondViewportPageCount from HorizontalPager is when you really need to compose the adjacent items together with the visible items because you want the whole Paget to set its height to the height of the larger page including those extra item. As otherwise the height will be only using the heights of the currently visible items and "jump" once you scroll to the new larger page. For that use case we introduced this api into Pager, but are not seeing good reasons to add it into lazy lists for now ”