Skip to content

Add a note to release notes about inline functions with compile avoidance #15121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 11, 2020
Merged

Add a note to release notes about inline functions with compile avoidance #15121

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions subprojects/docs/src/docs/release/notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,11 @@ A non-ABI change can [eliminate build script recompilation altogether now](https
While changes to `buildSrc` immediately affect the classpath of all the scripts, this improvement is more general and applies to changes in
any jar on the scripts classpath that can be added by a plugin applied from an included build or added directly via `buildscript {}` block.

**Note**: Kotlin's public [inline functions](https://kotlinlang.org/docs/reference/inline-functions.html#inline-functions) are not supported with compilation avoidance.
If such functions appear in the public API of a jar on the buildscript's classpath, that jar will not participate in compilation avoidance.
For example, if `buildSrc` contains a class with a public inline function, then `buildSrc` will not participate in compilation avoidance and all
the buildscripts will be recompiled for any change in `buildSrc`.

### Improved cache hits when normalizing runtime classpaths

For [up-to-date checks](userguide/more_about_tasks.html#sec:up_to_date_checks) and the [build cache](userguide/build_cache.html), Gradle needs to determine if two task input properties have the same value. In order to do so, Gradle first [normalizes](userguide/more_about_tasks.html#sec:configure_input_normalization) both inputs and then compares the result.
Expand Down