commit | a330c0d3bcdd41326f37968a60e6084ad4a2e32c | [log] [tgz] |
---|---|---|
author | Chet Haase <chet@google.com> | Wed Jul 05 07:26:46 2023 -0700 |
committer | Chet Haase <chet@google.com> | Mon Jul 10 16:07:28 2023 -0700 |
tree | 76e8bd4d82f9d97d2b92c7570f49ceb01069c4f6 | |
parent | c6af97e5f17f6fe60e0eff5630afe9840ef68787 [diff] |
Convert APIs using PointF to use Float instead PointF is a convenient mechanism for passing around x.y values representing 2D points. But there are downsides, including: - Converting to PointF: You may not have the data in PointF form to begin with, so using an API which takes PointF requires converting the data to that form (including allocating a PointF object every time) - Mutability: Point structures can be mutated internally, causing unpredictability in what that mutation means. Should the library react to those changes? Ignore them? Do defensive copies (requiring even more allocations)? Using primitive types like Float make the behavior more obvious (by making the data inherently immutable). - Allocations: Whenever we use object types, there are necessarily allocations on the Java heap for them. This puts pressure on the GC at both allocation and collection time. Given the amount of points being passed around (especially at morph creation time, when curves are being split and created), this causes a lot of PointF objects to be allocated (even temporarily). Using Float avoids that problem. Also fixed bug with unclosed paths causing discontinuity at the start/end point. Bug: 276466399 Bug: 290254314 Test: integration and unit tests pass Relnote: PointF parameters changed to Float pairs Change-Id: Id4705d27c7be31b26ade8186b99fffe2e2f8450e
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.