- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 14 for function (0.18 sec)
-
.cm/add_usual_expert.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
.cm/complex_changes.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.7K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/kotlin/gradlebuild/binarycompatibility/metadata/HasKotlinFlagsMetadataQuery.kt
import kotlinx.metadata.KmConstructor import kotlinx.metadata.KmFunction import kotlinx.metadata.KmPackage import kotlinx.metadata.KmProperty import kotlinx.metadata.jvm.KotlinClassMetadata import kotlinx.metadata.jvm.fieldSignature import kotlinx.metadata.jvm.getterSignature import kotlinx.metadata.jvm.setterSignature import kotlinx.metadata.jvm.signature import java.util.function.Supplier internal
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Wed Jun 07 08:14:15 GMT 2023 - 4.5K bytes - Viewed (0) -
.cm/lacks_tests.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2.4K bytes - Viewed (0) -
.teamcity/src/main/kotlin/model/bucket-extensions.kt
* * @param list the list to split, must be ordered by size desc * @param toIntFunction the function used to map the element to its "size" * @param largeElementSplitFunction the function used to further split the large element into smaller pieces * @param smallElementAggregateFunction the function used to aggregate tiny elements into a large bucket
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Nov 17 05:17:44 GMT 2022 - 4K bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/kotlin/gradlebuild/binarycompatibility/metadata/KotlinMetadataQueries.kt
else hasKotlinFlag(ctMember, Flag.IS_INTERNAL) fun isKotlinOperatorFunction(ctMethod: CtMethod): Boolean = hasKotlinFlag(ctMethod, Flag.Function.IS_OPERATOR) fun isKotlinInfixFunction(ctMethod: CtMethod): Boolean = hasKotlinFlag(ctMethod, Flag.Function.IS_INFIX) private fun hasKotlinFlag(ctClass: CtClass, flag: Flag): Boolean = queryKotlinMetadata(ctClass, false) { metadata ->
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Wed Jun 07 08:20:38 GMT 2023 - 4.6K bytes - Viewed (0) -
.cm/platform_labels.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Apr 22 15:32:31 GMT 2024 - 2.5K bytes - Viewed (0) -
.cm/misc_labels.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 3K bytes - Viewed (0) -
.cm/summary_table_platforms.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0)