* is not observed after a sufficient number of reads, try cleaning up from the read thread.
     */
    void postReadCleanup() {
      if ((readCount.incrementAndGet() & DRAIN_THRESHOLD) == 0) {
        cleanUp();
      }
    }

    /**
     * Performs routine cleanup prior to executing a write. This should be called every time a write
     * thread acquires the segment lock, immediately after acquiring the lock.

Mas antes disso, controlar código assíncrono era bem mais complexo e difícil.

Nas versões anteriores do Python, você poderia utilizar threads ou [Gevent](https://www.gevent.org/). Mas o código é bem mais complexo de entender, debugar, e pensar sobre.

Nas versões anteriores do NodeJS / Navegador JavaScript, você utilizaria "callbacks". O que leva ao "inferno do callback".

labels.includedDocPaths=Caminhos a serem incluídos na pesquisa
labels.includedDocUrls=URLs a serem incluídas na pesquisa
labels.maxAccessCount=Número máximo de acessos
labels.name=Nome
labels.numOfThread=Número de threads
labels.duplicateHostName=Nome duplicado
labels.pageNumber=Número da página
labels.password=Senha
labels.paths=Caminhos
labels.port=Porta
labels.regex=Expressão regular
labels.regularName=Nome regular

    /** The key of the message: Name */
    public static final String LABELS_NAME = "{labels.name}";

    /** The key of the message: Number of Threads */
    public static final String LABELS_NUM_OF_THREAD = "{labels.numOfThread}";

    /** The key of the message: Duplicate Host Name */
    public static final String LABELS_DUPLICATE_HOST_NAME = "{labels.duplicateHostName}";

needed to link programs that import package net.

Runtime

When using cgo, Go must not assume that it owns all details of the
process. In particular it needs to coordinate with C in the use of
threads and thread-local storage. The runtime package declares a few
variables:

	var (
		iscgo             bool
		_cgo_init         unsafe.Pointer
		_cgo_thread_start unsafe.Pointer
	)

     * is not observed after a sufficient number of reads, try cleaning up from the read thread.
     */
    void postReadCleanup() {
      if ((readCount.incrementAndGet() & DRAIN_THRESHOLD) == 0) {
        cleanUp();
      }
    }

    /**
     * Performs routine cleanup prior to executing a write. This should be called every time a write
     * thread acquires the segment lock, immediately after acquiring the lock.

{* ../../docs_src/sql_databases/tutorial001_an_py310.py ln[14:18] hl[14:15,17:18] *}

Usar `check_same_thread=False` permite que o FastAPI use o mesmo banco de dados SQLite em diferentes threads. Isso é necessário, pois **uma única requisição** pode usar **mais de uma thread** (por exemplo, em dependências).

Davor war der Umgang mit asynchronem Code jedoch deutlich komplexer und schwieriger.

In früheren Versionen von Python hätten Sie Threads oder [Gevent](https://www.gevent.org/) verwenden können. Der Code ist jedoch viel komplexer zu verstehen, zu debuggen und nachzuvollziehen.

labels.includedDocPaths=Eingeschlossene Pfade für die Suche
labels.includedDocUrls=Eingeschlossene URLs für die Suche
labels.maxAccessCount=Maximale Zugriffsanzahl
labels.name=Name
labels.numOfThread=Anzahl der Threads
labels.duplicateHostName=Doppelter Hostname
labels.pageNumber=Seitennummer
labels.password=Passwort
labels.paths=Pfade
labels.port=Port
labels.regex=Regulärer Ausdruck
labels.regularName=Regulärer Name

labels.includedDocPaths=Pad(en) om op te nemen in zoeken
labels.includedDocUrls=URL(s) om op te nemen in zoeken
labels.maxAccessCount=Maximaal aantal toegangspogingen
labels.name=Naam
labels.numOfThread=Aantal threads
labels.duplicateHostName=Dubbele naam
labels.pageNumber=Paginanummer
labels.password=Wachtwoord
labels.paths=Paden
labels.port=Poort
labels.regex=Reguliere expressie
labels.regularName=Reguliere naam