- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for ADR (0.17 sec)
-
architecture/standards/0005-introduce-core-ui-architecture-module.md
# ADR-0004 - Introduce a UI architecture module to the core platform ## Date 2024-02-07 ## Context The Gradle core platform provides many services to the Gradle platforms and builds logic. One such group of services allows logic to interact with the build user, to provide diagnostics, progress information, prompt for questions, and so on. Currently, these services are part of the core platform runtime architecture module.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Mar 04 23:19:15 GMT 2024 - 1.3K bytes - Viewed (0) -
architecture/standards/README.md
For now we just have this global repository of ADRs. If we see fit, we can break these out to per-platform ones, or keep a hybrid approach to having global and platform-specific ADSs. Our aim is to keep the process lightweight and approachable.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Feb 21 06:30:44 GMT 2024 - 546 bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
Like code, they should be reviewed by any other relevant teams. The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together. ### Format The format for ADR should follow this template: ```markdown # ADR-000X - Title ## Date 20YY-MM-DD ## Context Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0) -
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
# ADR-0003 - Avoid introducing Groovy types to public API ## Date 2024-01-12 ## Context Gradle's public API requires equal access from all JVM-based languages. Kotlin, Groovy, Java, and other JVM-based languages should be able to use the Gradle API without relying on another language's standard library. Historically, Gradle has shipped with some Groovy types in very prominent APIs.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Mar 10 20:38:06 GMT 2024 - 1.8K bytes - Viewed (0) -
architecture/standards/0002-avoid-using-java-serialization.md
# ADR-0002 - Avoid using Java serialization ## Date 2012-12-01 ## Context In Gradle we often need to serialize in-memory objects for caching, or to transmit them across process barriers, etc. Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks: - **Performance:** Java's built-in serialization mechanism is often slower compared to other serialization solutions.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0) -
src/cmd/asm/internal/asm/testdata/arm64.s
BEQ 1(PC) BEQ 2(PC) TBZ $1, R1, 2(PC) TBNZ $2, R2, 2(PC) JMP foo(SB) CALL foo(SB) // ADR ADR next, R11 // ADR R11 // 2b000010 next: NOP ADR -2(PC), R10 // 0a000010 ADR 2(PC), R16 // 10000010 ADR -26(PC), R1 // 01000010 ADR 12(PC), R2 // 02000010 ADRP -2(PC), R10 // 0a000090 ADRP 2(PC), R16 // 10000090 ADRP -26(PC), R1 // 01000090
Others - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Dec 08 03:28:17 GMT 2023 - 94.9K bytes - Viewed (0) -
architecture/standards/0004-use-a-platform-architecture.md
# ADR-0004 - Use a platform-oriented architecture for Gradle ## Date 2024-02-07 ## Context The Gradle code base is essentially a large monolith, without strong internal boundaries. This has a number of negative effects on productivity, including: - Unclear ownership of code. - Difficult to focus on one particular area. - Unintended coupling between areas of the code, including tests. ## Decision
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Feb 25 22:19:29 GMT 2024 - 4.5K bytes - Viewed (0) -
src/cmd/asm/internal/asm/asm.go
} p.errorf("wrong number of arguments to %s instruction", op) return case 1: target = &a[0] case 2: // Special 2-operand jumps. if p.arch.Family == sys.ARM64 && arch.IsARM64ADR(op) { // ADR label, R. Label is in From. target = &a[0] prog.To = a[1] targetAddr = &prog.From } else { target = &a[1] prog.From = a[0] } case 3: if p.arch.Family == sys.PPC64 {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Feb 21 14:34:57 GMT 2024 - 25.3K bytes - Viewed (0)