<!-- go.dev/issue/77177 -->

Response file (`@file`) parsing is now supported for the `compile`, `link`, `asm`, `cgo`, `cover`, and `pack` tools.
The response file contains whitespace-separated arguments with support for single-quoted and double-quoted strings, escape sequences, and backslash-newline line continuation.
The format is compatible with GCC's response file implementation to ensure interoperability with existing build systems.

### Go command {#go-command}

      var value =
        if (equalsSign < pairEnd) {
          header.trimSubstring(equalsSign + 1, pairEnd)
        } else {
          ""
        }

      // If the value is "quoted", drop the quotes.
      if (value.startsWith("\"") && value.endsWith("\"") && value.length >= 2) {
        value = value.substring(1, value.length - 1)
      }

        }
    }

    @Test
    public void test_complex_query_strings() {
        // Test various complex query strings
        String[] queryStrings = { "title:test", "content:\"quoted value\"", "field:value AND other:value", "field:value OR other:value",
                "field:[1 TO 100]", "field:value*", "field:?value", "field:~value", "field:value^2", "タイトル:テスト", "标题:测试", "제목:테스트" };

        "$@"

# Stop when "xargs" is not available.
if ! command -v xargs >/dev/null 2>&1
then
    die "xargs is not available"
fi

# Use "xargs" to parse quoted args.
#
# With -n1 it outputs one arg per line, with the quotes and backslashes removed.
#
# In Bash we could simply go:
#
#   readarray ARGS < <( xargs -n1 <<<"$var" ) &&
#   set -- "${ARGS[@]}" "$@"
#

are discarded from the raw string value.
</p>

<p>
Interpreted string literals are character sequences between double
quotes, as in <code>&quot;bar&quot;</code>.
Within the quotes, any character may appear except newline and unescaped double quote.
The text between the quotes forms the
value of the literal, with backslash escapes interpreted as they

        `tf.contrib.data.choose_from_datasets()` make it easier to sample or
        deterministically choose elements from multiple datasets.
    *   `tf.contrib.data.make_csv_dataset()` now supports line breaks in quoted
        strings, and two infrequently used arguments removed.
    *   (C++) `DatasetBase::DebugString()` is now `const`.
    *   (C++) `DatasetBase::MakeIterator()` has been renamed to

    assertBasicXmlEscaper(xmlAttributeEscaper, true, true);
    // Test quotes are escaped.
    assertThat(xmlAttributeEscaper.escape("\"test\"")).isEqualTo(""test"");
    assertThat(xmlAttributeEscaper.escape("'test'")).isEqualTo("'test'");
    // Test all escapes
    assertThat(xmlAttributeEscaper.escape("a\"b<c>d&e\"f'"))
        .isEqualTo("a&quot;b&lt;c&gt;d&amp;e&quot;f&apos;");
    // Test '\t', '\n' and '\r' are escaped.

)

var (
	currentTable  = Table{Name: CurrentTable}
	PrimaryColumn = Column{Table: CurrentTable, Name: PrimaryKey}
)

// Column quote with name
type Column struct {
	Table string
	Name  string
	Alias string
	Raw   bool
}

// Table quote with name
type Table struct {
	Name  string
	Alias string
	Raw   bool

///

////

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

Автор підсказки може обрати, чи конвертувати нейтральні лапки в типографські. Можна залишити як є.

Див., наприклад, розділ `### Quotes` у `docs/de/llm-prompt.md`.

////

## Лапки у фрагментах коду { #quotes-in-code-snippets }

//// tab | Тест

`pip install "foo[bar]"`

Приклади строкових літералів у фрагментах коду: `"this"`, `'that'`.

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

Автор промпта может выбрать, хочет ли он преобразовывать нейтральные кавычки в типографские. Допускается оставить их как есть.

См., например, раздел `### Quotes` в `docs/de/llm-prompt.md`.

////

## Кавычки во фрагментах кода { #quotes-in-code-snippets }

//// tab | Тест

`pip install "foo[bar]"`

Примеры строковых литералов во фрагментах кода: `"this"`, `'that'`.