Ik denk dat `Union[SomeType, None]` explicieter is over wat het betekent.

Het gaat alleen om de woorden en naamgeving. Maar die naamgeving kan invloed hebben op hoe jij en je teamgenoten over de code denken.

Laten we als voorbeeld deze functie nemen:

{* ../../docs_src/python_types/tutorial009c.py hl[1,4] *}

labels.webApiJson=JSON-antwoord
labels.webConfigName=Webcrawlconfiguratienaam
labels.allLanguages=Alle talen
labels.dictId=Woordenboek-ID
labels.docId=Document-ID
labels.endTime=Eindtijd
labels.hq=hq
labels.inputs=Invoer
labels.jobLogging=Loggen
labels.jobName=Naam
labels.jobStatus=Status
labels.labelTypeIds=Labels
labels.lang=Taal
labels.outputs=Uitvoer
labels.pos=Woordsoort

c.storage[:len(key)] copy(c.key, key) return c } // BlockFunction returns the function code for the block cipher. // It is used by the GCM implementation to invoke the KMA instruction. func BlockFunction(c *Block) int { return int(c.function) } // BlockKey returns the key for the block cipher. // It is used by the GCM implementation to invoke the KMA instruction. func BlockKey(c *Block) []byte { return c.key } func encryptBlock(c *Block, dst, src []byte) { if c.fallback != nil { encryptBlockGeneric(c.fallback,...

			}
		}
		if err := store.deleteUserIdentity(ctx, ui.Credentials.AccessKey, stsUser); err != nil {
			return err
		}
		delete(cache.iamSTSAccountsMap, ui.Credentials.AccessKey)
		revoked = true
	}

	if revoked {
		cache.updatedAt = time.Now()
	}

	return nil
}

// DeleteUsers - given a set of users or access keys, deletes them along with

				iamLogIf(ctx, nerr.Err)
			}
		}
	}
	return updatedAt, nil
}

// RevokeTokens - revokes all STS tokens, or those of specified type, for a user
// If `tokenRevokeType` is empty, all tokens are revoked.
func (sys *IAMSys) RevokeTokens(ctx context.Context, accessKey, tokenRevokeType string) error {
	if !sys.Initialized() {
		return errServerNotInitialized
	}

            if (!this.endDate) {
                this.startDate = this.oldStartDate.clone();
                this.endDate = this.oldEndDate.clone();
            }

            //if a new date range was selected, invoke the user callback function
            if (!this.startDate.isSame(this.oldStartDate) || !this.endDate.isSame(this.oldEndDate))
                this.callback(this.startDate.clone(), this.endDate.clone(), this.chosenLabel);

        } else {
          throw IllegalStateException()
        }
        if (name == "expect" && value.equals("100-continue", ignoreCase = true)) {
          // Don't read the body unless we've invited the client to send it.
          readBody = false
        }
      }
      val headers = httpHeaders.build()

      val peek = dispatcher.peek()
      for (response in peek.informationalResponses) {

</p>

<p>
A data race is defined as
a write to a memory location happening concurrently with another read or write to that same location,
unless all the accesses involved are atomic data accesses as provided by the <code>sync/atomic</code> package.
As noted already, programmers are strongly encouraged to use appropriate synchronization
to avoid data races.

	public abstract fun withWriteTimeout (ILjava/util/concurrent/TimeUnit;)Lokhttp3/Interceptor$Chain;
	public abstract fun writeTimeoutMillis ()I
}

public final class okhttp3/Interceptor$Companion {
	public final fun invoke (Lkotlin/jvm/functions/Function1;)Lokhttp3/Interceptor;
}

public final class okhttp3/MediaType {
	public static final field Companion Lokhttp3/MediaType$Companion;

    general mechanism. The dispatcher now exposes all in-flight calls via its
    `runningCalls()` and `queuedCalls()` methods. You can write code that
    selects calls by tag, host, or whatever, and invokes `Call.cancel()` on the
    ones that are no longer necessary.

 *  **OkHttp no longer uses the global `java.net.Authenticator` by default.**
    We've changed our `Authenticator` interface to authenticate web and proxy