commit | b536dfc662060df0264eb103247ad5161abb5074 | [log] [tgz] |
---|---|---|
author | Steven Schäfer <stevenschaefer@google.com> | Tue Oct 11 16:14:35 2022 +0200 |
committer | Steven Schäfer <stevenschaefer@google.com> | Wed Nov 02 15:42:50 2022 +0100 |
tree | fecda6d9ce2f37bccea30c3857e645eae898a66a | |
parent | 03bfa916540130c38766073091a1c13700f27aa3 [diff] |
Use `JvmIrCodegenFactory` in IR transform tests... ...rather than relying on internal psi2ir APIs. Using psi2ir directly allowed the tests to go out of sync with the Kotlin compiler. Additionally, this CL contains a number of smaller fixes and refactorings: - Fix `irForLoop` in `AbstractComposeLowering.kt`. This code broke `testPrimitiveVarargParams` in recent Kotlin compiler versions, due to unbound symbols in `BuiltInSymbolsBase`. This went unnoticed since `JvmCompilation.compile` did not have this problem. - Register an `IrMessageLogger` in tests to see backend errors and warnings. - Remove `CompilerConfiguration` parameter from `ComposeIrGeneratorExtension`, since it duplicates all other configuration parameters and may not be available when we instantiate the extension for tests. - Introduce `AbstractLiveLiteralTransformTests` to remove shared code from `LiveLiteralTransform*Test`. - Remove `ComposeIrTransformTest`, since all subclasses of `AbstractIrTransformTest` were running IR transform tests using the Compose plugin. - Split the extension point registration in `ComposePlugin.kt` into common (i.e., frontend) extension points and the IR extension point. This allows all tests to run the frontend checks from the plugin even if they need to register a different IR generation extension. - Preserve `IrIfThenElseImpl` in `DeepCopyIrTreeWithSymbolsPreservingMetadata`, since this affects the printing in `IrSourcePrinter`. - Set `correspondingPropertySymbol`s in `LiveLiteralTransformer`. This pass was technically producing invalid IR, but this was fixed up when running the IR through `DeepCopyIrTreeWithSymbols` in `ComposerParamTransformer`. Test: ./gradlew :compose:compiler:c-h:i-t:tDUT Change-Id: I6d11728db288e41647dccfc331c60b5e4498dda5
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()
, jcenter()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.