type RWLocker interface {
	GetLock(ctx context.Context, timeout *dynamicTimeout) (lkCtx LockContext, timedOutErr error)
	Unlock(lkCtx LockContext)
	GetRLock(ctx context.Context, timeout *dynamicTimeout) (lkCtx LockContext, timedOutErr error)
	RUnlock(lkCtx LockContext)
}

// LockContext lock context holds the lock backed context and canceler for the context.
type LockContext struct {
	ctx    context.Context

import java.lang.annotation.Documented;
import java.lang.annotation.Retention;
import java.lang.annotation.Target;

import static java.lang.annotation.ElementType.METHOD;
import static java.lang.annotation.ElementType.TYPE;
import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Indicates that annotated component should be instantiated before session execution starts
 * and discarded after session execution completes.
 * <p>

    /**
     * Gets the remote host name for this tree connection
     * @return the remote host name
     */
    String getRemoteHostName();

    /**
     * Gets the tree type (share type such as disk, printer, pipe, etc.)
     * @return the tree type
     */
    int getTreeType();

    /**
     * Gets the name of the file or directory.
     *
     * @return the file or directory name
     */
    String getName();

    /**
     * Gets the type of the entry.
     *
     * @return the entry type
     */
    int getType();

    /**
     * Gets the file attributes.
     *
     * @return the file attributes
     */
    int getAttributes();

    /**

</div>
<c:if test="${partialResults}">
	<div class="alert">
		<p>
			<la:message key="labels.process_time_is_exceeded" />
		</p>
	</div>
</c:if>
<div id="result" class="row">
	<input type="hidden" id="queryId" value="${f:h(queryId)}" /> <input
		type="hidden" id="rt" value="${f:h(requestedTime)}" />
	<ol class="list-unstyled col-md-8">
		<c:forEach var="doc" varStatus="s" items="${documentItems}">
			<li id="result${s.index}">

//
// - The object should be present in all buckets accessed by Veeam products that want to leverage the SOSAPI functionality.
//
// - The current protocol version is 1.0.
type apiEndpoints struct {
	IAMEndpoint string `xml:"IAMEndpoint"`
	STSEndpoint string `xml:"STSEndpoint"`
}

// globalVeeamForceSC is set by the environment variable _MINIO_VEEAM_FORCE_SC

     * This is a required field describing what the job operated on.
     */
    @Required
    public String target;

    /**
     * The type of script that was executed for this job.
     * This is a required field indicating the script engine or type used.
     */
    @Required
    public String scriptType;

    /**
     * The script data or code that was executed.

		vID, err := uuid.Parse(fi.TierFreeVersionID())
		if err != nil {
			panic(fmt.Errorf("Invalid Tier Object delete marker versionId %s %v", fi.TierFreeVersionID(), err))
		}
		freeEntry := xlMetaV2Version{Type: DeleteType, WrittenByVersion: globalVersionUnix}
		freeEntry.DeleteMarker = &xlMetaV2DeleteMarker{
			VersionID: vID,
			ModTime:   j.ModTime, // fi.ModTime may be empty
			MetaSys:   make(map[string][]byte),
		}

C'était l'une des premières implémentations d'un framework utilisant les type hints Python pour déclarer les paramètres
et les requêtes que j'ai vues (avant NestJS et Molten). Je l'ai trouvé plus ou moins en même temps que Hug. Mais APIStar utilisait le standard OpenAPI.

Il disposait de la validation automatique, sérialisation des données et d'une génération de schéma OpenAPI basée sur les mêmes type hints à plusieurs endroits.

    /** The type of the underlying query builder. */
    private final QueryType queryType;

    /**
     * Creates a new DefaultQueryBuilder wrapping the specified QueryBuilder.
     *
     * @param queryBuilder the query builder to wrap (must be BoolQueryBuilder or DisMaxQueryBuilder)
     * @throws IllegalArgumentException if the query builder type is not supported
     */