constraints.DecimalMax.message = {item} musi być mniejsze niż {value}.
constraints.DecimalMin.message = {item} musi być większe niż {value}.
constraints.Digits.message = {item} musi być liczbą. (Oczekiwano: <liczba>.<liczba>)
constraints.Future.message = {item} musi być wartością przyszłą.
constraints.Max.message = {item} musi być mniejsze lub równe {value}.
constraints.Min.message = {item} musi być większe lub równe {value}.

   * worker, and then the first thread's call to delegate.execute() returns. Without this counter,
   * it would observe the QUEUING state and set it to QUEUED, and the worker would never be
   * scheduled again for future submissions.
   */
  @GuardedBy("queue")
  private long workerRunCount = 0;

  @RetainedWith private final QueueWorker worker = new QueueWorker();

  /** Use {@link MoreExecutors#newSequentialExecutor} */

   * worker, and then the first thread's call to delegate.execute() returns. Without this counter,
   * it would observe the QUEUING state and set it to QUEUED, and the worker would never be
   * scheduled again for future submissions.
   */
  @GuardedBy("queue")
  private long workerRunCount = 0;

  @RetainedWith private final QueueWorker worker = new QueueWorker();

  /** Use {@link MoreExecutors#newSequentialExecutor} */

}

type ConnPool interface {
	PrepareContext(ctx context.Context, query string) (*sql.Stmt, error)
}

// New creates a new Stmt object for executing SQL queries.
// It caches the Stmt object for future use and handles preparation and error states.
// Parameters:
//
//	ctx: Context for the request, used to carry deadlines, cancellation signals, etc.

constraints.DecimalMin.message = {item} deve ser maior que {value}.
constraints.Digits.message = {item} deve ser um número. (Esperado: <número>.<número>)
constraints.Future.message = {item} deve ser uma data futura.
constraints.Max.message = {item} deve ser menor ou igual a {value}.
constraints.Min.message = {item} deve ser maior ou igual a {value}.
constraints.NotNull.message = {item} é obrigatório.

constraints.AssertTrue.message = {item} 必须为 true。
constraints.DecimalMax.message = {item} 必须小于 {value}。
constraints.DecimalMin.message = {item} 必须大于 {value}。
constraints.Digits.message = {item} 必须是数字。(预期: <数字>.<数字>)
constraints.Future.message = {item} 必须是未来的值。
constraints.Max.message = {item} 必须小于或等于 {value}。
constraints.Min.message = {item} 必须大于或等于 {value}。
constraints.NotNull.message = {item} 不能为空。
constraints.Null.message = {item} 必须为 null。

 *          Javadoc description provided.<br>
 *          <i>NOTE: While this is not a required part of the Mojo specification, it <b>SHOULD</b> be provided to
 *          enable future tool support for browsing, etc. and for clarity.</i>
 *      </td>
 *   </tr>
 *   <tr>
 *      <td>parameters</td>
 *      <td>N/A</td>
 *      <td>No</td>

            <caution>
                <para>Note: This property is <ulink url="../userguide/feature_lifecycle.html">incubating</ulink> and may change in a future version of Gradle.</para>
            </caution>
            <para>prop2 comment</para>
        </section>
    </section>
</chapter>'''
    }

   *
   * @param key the non-null key whose value should be loaded
   * @param oldValue the non-null old value corresponding to {@code key}
   * @return the future new value associated with {@code key}; <b>must not be null, must not return
   *     null</b>
   * @throws Exception if unable to reload the result

       * make a ton of sense to have a separate tests for each. But having tests for each doesn't
       * really hurt anything, and maybe it will serve a purpose in a future in which Java has a
       * built-in nullness feature?
       */
      "ExtendsObject",
    })
    <T extends Object> void withObjectBound(List<T> list) {}

    @SuppressWarnings("unused")