Home
last modified time | relevance | path

Searched full:breaking (Results 1 – 25 of 3047) sorted by relevance

12345678910>>...122

/external/rust/android-crates-io/crates/libtest-mimic/
DCHANGELOG.md21 - **Breaking**: Updated `clap` to version 4 (thanks @msrd0)
22 - **Breaking**: Bump MSRV to 1.60 (due to the clap update)
25 - **Breaking**: Remove `FromStr` impls for `args::{ColorSetting, FormatSetting}` (use `clap::ValueE…
46 - **Breaking**: bump MSRV to 1.58
47 - **Breaking**: Rename `Test` to `Trial`
48 - **Breaking**: Rename `run_tests` to `run`
49 - ⭐ **Breaking**: Make every `Trial` have a runner function instead of `data` + a
52 - **Breaking**: Add `Trial::{test, bench}` constructor functions, use builder
54 - **Breaking**: rename `Args::num_threads` to `test_threads`
55 - **Breaking**: make fields of `Conclusion` public and remove getter methods
[all …]
/external/bazelbuild-rules_python/
DCONTRIBUTING.md132 BREAKING CHANGE: <summary>
135 Where `(scope)` is optional, and `!` is only required if there is a breaking change.
136 If a breaking change is introduced, then `BREAKING CHANGE:` is required; see
137 the [Breaking Changes](#breaking-changes) section for how to introduce breaking
187 (breaking-changes)=
188 ## Breaking Changes
190 Breaking changes are generally permitted, but we follow a 3-step process for
214 ### How to control breaking changes
237 ### What is considered a breaking change?
239 Precisely defining what constitutes a breaking change is hard because it's
[all …]
/external/cronet/tot/third_party/boringssl/src/
DBREAKING-CHANGES.md3 …projects because we have a reasonable idea of who our users are. Still, breaking changes require s…
5 Ultimately, the strategy for each breaking change is decided on a case-by-case basis. This document…
9 …breaking changes are defined in terms of API or ABI surface. Exposed symbols and type signatures c…
11 …do not think about whether a change is formally a breaking change, but about the *risk* of it brea…
43 1. Upload the breaking change to Gerrit, but do not submit it yet. Increment the `BORINGSSL_API_VER…
54 When breaking changes do occur, they should fail as early and as detectably as possible.
60 If breaking the compile is not feasible, break at runtime, in the hope that consumers have some amo…
66 While we try to avoid breaking things, sometimes things unexpectedly break. Depending on the impact…
72 When planning a large project that depends on a breaking change, prefer to make the breaking change…
80 …ntain patches for this as necessary, it has overhead and so the cost of breaking third-party code …
/external/cronet/stable/third_party/boringssl/src/
DBREAKING-CHANGES.md3 …projects because we have a reasonable idea of who our users are. Still, breaking changes require s…
5 Ultimately, the strategy for each breaking change is decided on a case-by-case basis. This document…
9 …breaking changes are defined in terms of API or ABI surface. Exposed symbols and type signatures c…
11 …do not think about whether a change is formally a breaking change, but about the *risk* of it brea…
43 1. Upload the breaking change to Gerrit, but do not submit it yet. Increment the `BORINGSSL_API_VER…
54 When breaking changes do occur, they should fail as early and as detectably as possible.
60 If breaking the compile is not feasible, break at runtime, in the hope that consumers have some amo…
66 While we try to avoid breaking things, sometimes things unexpectedly break. Depending on the impact…
72 When planning a large project that depends on a breaking change, prefer to make the breaking change…
80 …ntain patches for this as necessary, it has overhead and so the cost of breaking third-party code …
/external/boringssl/src/
DBREAKING-CHANGES.md3 …projects because we have a reasonable idea of who our users are. Still, breaking changes require s…
5 Ultimately, the strategy for each breaking change is decided on a case-by-case basis. This document…
9 …breaking changes are defined in terms of API or ABI surface. Exposed symbols and type signatures c…
11 …do not think about whether a change is formally a breaking change, but about the *risk* of it brea…
43 1. Upload the breaking change to Gerrit, but do not submit it yet. Increment the `BORINGSSL_API_VER…
54 When breaking changes do occur, they should fail as early and as detectably as possible.
60 If breaking the compile is not feasible, break at runtime, in the hope that consumers have some amo…
66 While we try to avoid breaking things, sometimes things unexpectedly break. Depending on the impact…
72 When planning a large project that depends on a breaking change, prefer to make the breaking change…
80 …ntain patches for this as necessary, it has overhead and so the cost of breaking third-party code …
/external/sdv/vsomeip/third_party/boost/thread/doc/
Dconfiguration.qbk105 [warning This is a breaking change respect to version 1.x.]
118 [warning This is a breaking change respect to version 1.x.]
156 [warning This is a breaking change respect to version 1.x.]
296 [warning This is a breaking change respect to version 3.x.]
325 [warning This is a breaking change respect to version 3.x.]
346 The default version is 2. In this case the following breaking or extending macros are defined if th…
350 …n 3 by defining `BOOST_THREAD_VERSION` to 3. In this case the following breaking or extending macr…
352 * Breaking change `BOOST_THREAD_PROVIDES_EXPLICIT_LOCK_CONVERSION `
353 * Conformity & Breaking change `BOOST_THREAD_PROVIDES_FUTURE`
357 * Conformity & Breaking change BOOST_THREAD_PROVIDES_THREAD_DESTRUCTOR_CALLS_TERMINATE_IF_JOINABLE
[all …]
/external/grpc-grpc/doc/
Dversioning.md15 …they reach 1.0, they are considered not ready for production workloads. Breaking API changes are a…
27 … the language itself or its standard libraries that we depend on make a breaking change (something…
28 …breaking API change makes sense and represents a net win, but as a rule of thumb breaking changes …
29 Example scenarios where a breaking API change might be adequate:
30 …- fixing a security problem which requires changes to API (need to consider the non-breaking alter…
33 …All proposals to make a breaking change need to be documented as a gRFC document (in the grpc/prop…
34 …lanation why the proposed change is one of the very rare events where a breaking change is introdu…
45 …upporting evidence (see previous section), other strategy than making a breaking API change needs …
/external/rust/android-crates-io/crates/axum/
DCHANGELOG.md215 - **breaking:** The request `/foo/` no longer matches `/foo/*rest`. If you want
237 - **breaking:** Path params for wildcard routes no longer include the prefix
275 - **breaking:** Automatic trailing slash redirects have been removed.
297 - **breaking:** `Router::fallback` now only accepts `Handler`s (similarly to
321 - **breaking:** It is no longer supported to `nest` twice at the same path, i.e.
323 - **breaking:** It is no longer supported to `nest` a router and add a route at
328 - **breaking:** Allow `Error: Into<Infallible>` for `Route::{layer, route_layer}` ([#924])
329 - **breaking:** `MethodRouter` now panics on overlapping routes ([#1102])
330 - **breaking:** `Router::route` now only accepts `MethodRouter`s created with
333 - **breaking:** Adding a `.route_layer` onto a `Router` or `MethodRouter`
[all …]
/external/rust/android-crates-io/crates/axum-core/
DCHANGELOG.md38 - **breaking:** `FromRequest` has been reworked and `RequestParts` has been
40 - **breaking:** `BodyAlreadyExtracted` has been removed ([#1272])
41 - **breaking:** `AppendHeaders` now works on any `impl IntoIterator` ([#1495])
53 - **breaking:** `AppendHeaders` now works on any `impl IntoIterator` ([#1495])
61 - **breaking:** Added default limit to how much data `Bytes::from_request` will
78 - **breaking:** `FromRequest` has been reworked and `RequestParts` has been
82 - **breaking:** `BodyAlreadyExtracted` has been removed ([#1272])
91 - **breaking:** Added default limit to how much data `Bytes::from_request` will
161 - **breaking:** Using `HeaderMap` as an extractor will no longer remove the headers and thus
166 This includes these breaking changes:
[all …]
/external/cronet/tot/third_party/icu/patches/
Dwordbrk.patch10 +# Exclude '@' (commercial at, \u0040) from ALetter to maintain breaking at '@'.
11 +# ICU 49d192fefe09, in ICU 72, stopped breaking at '@' in order to not break up
18 +# previous Chromium behavior of breaking at both '@' and '.'.
29 +# to break a hostname into its components at the cost of breaking
51 +# Exclude '@' (commercial at, \u0040) from ALetter to maintain breaking at '@'.
52 +# ICU 49d192fefe09, in ICU 72, stopped breaking at '@' in order to not break up
59 +# previous Chromium behavior of breaking at both '@' and '.'.
87 +# Exclude '@' (commercial at, \u0040) from ALetter to maintain breaking at '@'.
88 +# ICU 49d192fefe09, in ICU 72, stopped breaking at '@' in order to not break up
95 +# previous Chromium behavior of breaking at both '@' and '.'.
[all …]
/external/cronet/stable/third_party/icu/patches/
Dwordbrk.patch10 +# Exclude '@' (commercial at, \u0040) from ALetter to maintain breaking at '@'.
11 +# ICU 49d192fefe09, in ICU 72, stopped breaking at '@' in order to not break up
18 +# previous Chromium behavior of breaking at both '@' and '.'.
29 +# to break a hostname into its components at the cost of breaking
51 +# Exclude '@' (commercial at, \u0040) from ALetter to maintain breaking at '@'.
52 +# ICU 49d192fefe09, in ICU 72, stopped breaking at '@' in order to not break up
59 +# previous Chromium behavior of breaking at both '@' and '.'.
87 +# Exclude '@' (commercial at, \u0040) from ALetter to maintain breaking at '@'.
88 +# ICU 49d192fefe09, in ICU 72, stopped breaking at '@' in order to not break up
95 +# previous Chromium behavior of breaking at both '@' and '.'.
[all …]
/external/google-cloud-java/java-monitoring/proto-google-cloud-monitoring-v3/src/main/java/com/google/monitoring/v3/
DBasicSliOrBuilder.java33 * that don't support breaking down by method, setting this field will result
49 * that don't support breaking down by method, setting this field will result
65 * that don't support breaking down by method, setting this field will result
82 * that don't support breaking down by method, setting this field will result
100 * activity. For service types that don't support breaking down by location,
116 * activity. For service types that don't support breaking down by location,
132 * activity. For service types that don't support breaking down by location,
149 * activity. For service types that don't support breaking down by location,
167 * that don't support breaking down by version, setting this field will result
183 * that don't support breaking down by version, setting this field will result
[all …]
/external/rust/android-crates-io/crates/bstr/scripts/regex/
Dsentence.sh11 # finite state machines for grapheme/sentence/word/line breaking is possible,
30 # A correct implementation of the sentence breaking algorithm should not insert
33 # without breaking them---which is correct---but will then start looking for
53 # tedious. With that said, we do no implement Unicode line breaking with this
81 # this by only permitting part of SB8a to match inside our core non-breaking
83 # permit the non-breaking components to continue. If a part of SB8a matches
86 # would allow moving back into SB998 and thus the non-breaking repetition, so
91 # UAX #29's recommendation in S6.2. Essentially, we use it avoid ever breaking
139 # In order to continue non-breaking matching, we now must observe
159 # As with ATerm above, in order to continue non-breaking matching, we
/external/chromiumos-config/
Dgenerate.sh40 --allow-breaking)
73 echo "== Checking for breaking protobuffer changes"
74 if ! buf breaking --against "${desc_file}"; then
79 One or more breaking changes detected. If these are intentional, re-run
80 with --allow-breaking to allow the changes.
86 One or more breaking changes, but --allow-breaking specified, continuing.
91 echo "No breaking changes, regenerating '${desc_file}'"
/external/rust/android-crates-io/crates/litrs/
DCHANGELOG.md21 - **Breaking**: Mark `FloatType` and `IntegerType` as `#[non_exhaustive]`
22 - **Breaking**: Fix integer parsing for cases like `27f32`. `Literal::parse`
24 - **Breaking**: Fix float parsing by correctly rejecting inputs like `27f32`. A
30 - **Breaking**: Remove `OwnedLiteral` and `SharedLiteral`
33 ### Breaking subsection
65 - **Breaking**: rename `Error` to `ParseError`. That describes its purpose more
69 - **Breaking**: remove `proc-macro` feature and instead offer the corresponding
/external/rust/android-crates-io/crates/icu_locale/src/
Dprovider.rs11 //! �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
23 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
185 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
236 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
314 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
360 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
390 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
446 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
468 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
/external/android_onboarding/java/com/android/onboarding/versions/changes/
DTestChanges.kt11 breaking = [],
19 breaking = [],
28 breaking = [],
38 breaking = [],
/external/rust/android-crates-io/crates/tempfile/
DCHANGELOG.md49 BREAKING: This release updates the MSRV to 1.63. This isn't an API-breaking change (so no major
50 release) but it's still a breaking change for some users.
70 - BREAKING: Remove the implementation of `Write for &NamedTempFile<F> where &F: Write`. Unfortunate…
101 Breaking:
131 Breaking: The minimum rust version is now `1.40.0`.
139 Breaking: The minimum rust version is now `1.32.0`.
155 Breaking: The minimum rust version is now 1.30.
169 Breaking:
/external/rust/android-crates-io/crates/icu_properties/src/provider/
Dnames.rs8 //! �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
248 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
271 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
295 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
320 /// �� This code is considered unstable; it may change at any time, in breaking or non-breaking way…
/external/grpc-grpc-java/xds/third_party/xds/src/main/proto/xds/annotations/v3/
Dstatus.proto24 // The entity is work-in-progress and subject to breaking changes.
29 // The entity is work-in-progress and subject to breaking changes.
34 // The entity is work-in-progress and subject to breaking changes.
54 // The entity is work-in-progress and subject to breaking changes.
/external/rust/android-crates-io/crates/grpcio-sys/grpc/third_party/xds/xds/annotations/v3/
Dstatus.proto24 // The entity is work-in-progress and subject to breaking changes.
29 // The entity is work-in-progress and subject to breaking changes.
34 // The entity is work-in-progress and subject to breaking changes.
54 // The entity is work-in-progress and subject to breaking changes.
/external/rust/android-crates-io/crates/aarch64-paging/
DCHANGELOG.md5 ### Breaking changes
17 ### Breaking changes
51 ### Breaking changes
77 ### Breaking changes
92 ### Breaking changes
123 ### Breaking changes
/external/rust/android-crates-io/crates/hound/
Dchangelog.md74 **Breaking changes**:
103 **Breaking changes**:
118 **Breaking changes**:
135 **Breaking changes**:
154 **Breaking changes**:
174 **Breaking changes**:
191 **Breaking changes**:
213 **Breaking changes**:
/external/crosvm/docs/book/src/running_crosvm/
Dprogrammatic_interaction.md25 updating the API surface. Any breaking change to a `crosvm_control` entrypoint must be handled the
26 same way as a breaking change to the crosvm CLI.
31 `crosvm_control` function will cause problems downstream and should be considered a breaking change.
35 For ChromeOS, it is possible to integrate a breaking change from upstream crosvm, but it should be
/external/android_onboarding/java/com/android/onboarding/versions/annotations/
DChangeId.kt13 * @param breaking Reasons that this change will cause breakages in current callers. Empty if none.
29 val breaking: Array<BreakingReason>, constant in com.android.onboarding.versions.annotations.ChangeId
44 …eId(bugId=${changeId.bugId}, owner=\"${changeId.owner}\", breaking=arrayOf(${changeId.breaking.joi… in generateChangeIdCode()

12345678910>>...122