Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 12 for atomically (0.06 sec)

  1. guava/src/com/google/common/util/concurrent/AtomicDoubleArray.java

      }
    
      /**
       * Atomically adds the given value to the element at index {@code i}.
       *
       * @param i the index
       * @param delta the value to add
       * @return the previous value
       */
      @CanIgnoreReturnValue
      public final double getAndAdd(int i, double delta) {
        return getAndAccumulate(i, delta, Double::sum);
      }
    
      /**
       * Atomically adds the given value to the element at index {@code i}.
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Mon Mar 17 20:26:29 UTC 2025
    - 10.2K bytes
    - Viewed (0)
  2. guava/src/com/google/common/util/concurrent/AtomicLongMap.java

    import java.util.function.LongBinaryOperator;
    import java.util.function.LongUnaryOperator;
    import org.jspecify.annotations.Nullable;
    
    /**
     * A map containing {@code long} values that can be atomically updated. While writes to a
     * traditional {@code Map} rely on {@code put(K, V)}, the typical mechanism for writing to this map
     * is {@code addAndGet(K, long)}, which adds a {@code long} to the value currently associated with
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Fri Oct 10 23:13:45 UTC 2025
    - 11.7K bytes
    - Viewed (0)
  3. src/test/java/jcifs/smb/SmbSessionImplSecurityTest.java

            session.release();
    
            // Then - Trees should be cleared (we can't directly verify as it's internal,
            // but the cleanup code with synchronized block ensures it happens atomically)
            // The important part is that no exception occurs and the operation is atomic
        }
    
        /**
         * Test concurrent acquire and release operations.
         */
        @Test
    Registered: Sat Dec 20 13:44:44 UTC 2025
    - Last Modified: Sun Aug 31 08:00:57 UTC 2025
    - 11K bytes
    - Viewed (0)
  4. android/guava/src/com/google/common/util/concurrent/AbstractScheduledService.java

           * This lock is used to ensure safe and correct cancellation, it ensures that a new task is
           * not scheduled while a cancel is ongoing. Also it protects the currentFuture variable to
           * ensure that it is assigned atomically with being scheduled.
           */
          private final ReentrantLock lock = new ReentrantLock();
    
          /** The future that represents the next execution of this task. */
          @GuardedBy("lock")
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Sat Aug 09 01:14:59 UTC 2025
    - 27.7K bytes
    - Viewed (0)
  5. guava/src/com/google/common/util/concurrent/AbstractScheduledService.java

           * This lock is used to ensure safe and correct cancellation, it ensures that a new task is
           * not scheduled while a cancel is ongoing. Also it protects the currentFuture variable to
           * ensure that it is assigned atomically with being scheduled.
           */
          private final ReentrantLock lock = new ReentrantLock();
    
          /** The future that represents the next execution of this task. */
          @GuardedBy("lock")
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Sat Aug 09 01:14:59 UTC 2025
    - 27.8K bytes
    - Viewed (0)
  6. android/guava-tests/benchmark/com/google/common/util/concurrent/MonitorBasedPriorityBlockingQueue.java

          E e;
          while (n < maxElements && (e = q.poll()) != null) {
            c.add(e);
            ++n;
          }
          return n;
        } finally {
          monitor.leave();
        }
      }
    
      /**
       * Atomically removes all of the elements from this queue. The queue will be empty after this call
       * returns.
       */
      @Override
      public void clear() {
        Monitor monitor = this.monitor;
        monitor.enter();
        try {
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Tue May 13 18:46:00 UTC 2025
    - 18.9K bytes
    - Viewed (0)
  7. guava-tests/benchmark/com/google/common/util/concurrent/MonitorBasedArrayBlockingQueue.java

      public String toString() {
        Monitor monitor = this.monitor;
        monitor.enter();
        try {
          return super.toString();
        } finally {
          monitor.leave();
        }
      }
    
      /**
       * Atomically removes all of the elements from this queue. The queue will be empty after this call
       * returns.
       */
      @Override
      public void clear() {
        E[] items = this.items;
        Monitor monitor = this.monitor;
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Tue May 13 18:46:00 UTC 2025
    - 22.4K bytes
    - Viewed (0)
  8. okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/RealCall.kt

      private val tags = AtomicReference(originalRequest.tags)
    
      override fun timeout(): Timeout = timeout
    
      override fun addEventListener(eventListener: EventListener) {
        // Atomically replace the current eventListener with a composite one.
        do {
          val previous = this.eventListener
        } while (!eventListenerUpdater.compareAndSet(this, previous, previous + eventListener))
      }
    
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Wed Nov 05 18:28:35 UTC 2025
    - 19.7K bytes
    - Viewed (0)
  9. okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2Connection.kt

          }
        }
    
        /**
         * Apply inbound settings and send an acknowledgement to the peer that provided them.
         *
         * We need to apply the settings and ack them atomically. This is because some HTTP/2
         * implementations (nghttp2) forbid peers from taking advantage of settings before they have
         * acknowledged! In particular, we shouldn't send frames that assume a new `initialWindowSize`
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Thu Jul 31 04:18:40 UTC 2025
    - 31.8K bytes
    - Viewed (0)
  10. docs/changelogs/changelog_4x.md

     *  Fix: Don't lose HTTP/2 flow control bytes when incoming data races with a stream close. If this
        happened enough then eventually the connection would stall.
    
     *  Fix: Acknowledge and apply inbound HTTP/2 settings atomically. Previously we had a race where we
        could use new flow control capacity before acknowledging it, causing strict HTTP/2 servers to
        fail the call.
    
    
    ## Version 4.1.1
    
    _2019-09-05_
    
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Wed Apr 17 13:25:31 UTC 2024
    - 25.2K bytes
    - Viewed (0)
Back to top