commit | fdcf01bdf0735b2738cce5a9acd5002ccbc5c55e | [log] [tgz] |
---|---|---|
author | Romain Guy <[email protected]> | Wed Oct 16 16:10:02 2024 -0700 |
committer | Romain Guy <[email protected]> | Mon Jan 06 10:45:11 2025 -0800 |
tree | 856128c2c5194d503cb0d90acc14591ceb0dc293 | |
parent | a1ec027bb75a9703f129b78c51bca3cf0921807d [diff] |
Optimize various things: Optimize array management: - Use @NeverInline in the cold code paths where we reallocate arrays to avoid putting a large amount of instructions on the hot path (caused by ART inlining). - Introduce fastCopyOfRange() to reduce the amount of generated code (exception/stack trace + string builder) by skipping parameters validation we don't need. - Introduce fastCopyInto() to eliminate unnecessary checks and exception throwing code introduced by the compiler after inlining. - Don't use copyOf() in the color space code, just create the array we need with the known values we need. It produces a lot less code. - Remove extra branches and instructions from IntStack. Other optimizations: - Branchless calls in ScrollNode - Skip static initialization checks in OpArray by removing the companion object we don't need. - Revert Constraints.bitsNeed...() and .maxAllowedForSize() to the original implementation. The dependent add operation we had to add is actually slightly worse on modern devices. It's better to keep the code simpler. - Unify padding checks in Padding.kt. Removes 60% of the branches on initialization. Optimize for the common case by switching to and instead of && in the test to go branchless. Factor method calls. - Use "fast" coerce implementations where possible. - Don't compare dps to Dp.Unspecified, use Dp.isSpecified instead (or Dp.isUnspecified). Same result, but much cheaper since we know Dp.Unspecified is NaN. - Cleanup: address various warnings. Test: ui tests, foundation tests, graphics tests Relnote: N/A Change-Id: I8402e8cfabf9726362273b2e7f5647854e602d63
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.