Сложный пример строковых литералов во фрагментах кода: `f"I like {'oranges' if orange else "apples"}"`

Хардкор: `Yesterday, my friend wrote: "If you spell incorrectly correctly, you have spelled it incorrectly". To which I answered: "Correct, but 'incorrectly' is incorrectly not '"incorrectly"'"`

////

//// tab | Информация

... Однако кавычки внутри фрагментов кода должны оставаться как есть.

////

 *
 * <p>This class is not threadsafe when any concurrent operations update the multimap, even if the
 * underlying map and {@link #createCollection()} method return threadsafe classes. Concurrent read
 * operations will work correctly. To allow concurrent update operations, wrap your multimap with a
 * call to {@link Multimaps#synchronizedMultimap}.
 *
 * <p>For serialization to work, the subclass must specify explicit {@code readObject} and {@code

    assertThat(c.eventSequence).isEmpty()
    assertThat(d.takeEvent()).isInstanceOf<CallStart>()
    assertThat(d.eventSequence).isEmpty()
  }

  /** Reflectively call every event function to confirm it is correctly forwarded. */
  @Test
  fun aggregateEventListenerIsComplete() {
    val sampleValues = sampleValuesMap()

    val solo = EventRecorder(enforceOrder = false)
    val left = EventRecorder(enforceOrder = false)

Ein schwieriges Beispiel für Stringliterale in Codeschnipseln: `f"I like {'oranges' if orange else "apples"}"`

Hardcore: `Yesterday, my friend wrote: "If you spell incorrectly correctly, you have spelled it incorrectly". To which I answered: "Correct, but 'incorrectly' is incorrectly not '"incorrectly"'"`

////

//// tab | Info

... Allerdings müssen Anführungszeichen in Codeschnipseln unverändert bleiben.

////

Складний приклад строкових літералів у фрагментах коду: `f"I like {'oranges' if orange else "apples"}"`

Хардкор: `Yesterday, my friend wrote: "If you spell incorrectly correctly, you have spelled it incorrectly". To which I answered: "Correct, but 'incorrectly' is incorrectly not '"incorrectly"'"`

////

//// tab | Інформація

... Однак лапки всередині фрагментів коду мають залишатися як є.

////

## Блоки коду { #code-blocks }

 * equals</i>. That is, {@code a.compareTo(b)} or {@code comparator.compare(a, b)} should equal zero
 * <i>if and only if</i> {@code a.equals(b)}. If this advice is not followed, the resulting map will
 * not correctly obey its specification.
 *
 * <p>See the Guava User Guide article on <a href=
 * "https://github.com/google/guava/wiki/ImmutableCollectionsExplained">immutable collections</a>.
 *
 * @author Jared Levy

代码片段中的字符串字面量示例：`"this"`，`'that'`。

一个较难的字符串字面量示例：`f"I like {'oranges' if orange else "apples"}"`

硬核：`Yesterday, my friend wrote: "If you spell incorrectly correctly, you have spelled it incorrectly". To which I answered: "Correct, but 'incorrectly' is incorrectly not '"incorrectly"'"`

////

//// tab | 信息

... 但是，代码片段内的引号必须保持不变。

////

## 代码块 { #code-blocks }

//// tab | 测试

一个 Bash 代码示例...

        assertEquals("Cp850", SmbConstants.DEFAULT_OEM_ENCODING);
        assertEquals(-1, SmbConstants.FOREVER);
    }

    @Test
    @DisplayName("Should validate flag combinations work correctly")
    void testFlagCombinations() {
        // Test that flags can be combined with bitwise OR
        int combinedShareAccess = SmbConstants.FILE_SHARE_READ | SmbConstants.FILE_SHARE_WRITE;

Un ejemplo difícil de literales de string en fragmentos de código: `f"I like {'oranges' if orange else "apples"}"`

Hardcore: `Yesterday, my friend wrote: "If you spell incorrectly correctly, you have spelled it incorrectly". To which I answered: "Correct, but 'incorrectly' is incorrectly not '"incorrectly"'"`

////

//// tab | Info

... Sin embargo, las comillas dentro de fragmentos de código deben quedarse tal cual.

////

* Ensure the backend pools are set correctly for Azure SLB with multiple backend pools (e.g. outbound rules) ([#76691](https://github.com/kubernetes/kubernetes/pull/76691), [@feiskyer](https://github.com/feiskyer))