- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 85 for awkward (0.24 sec)
-
okhttp/src/main/kotlin/okhttp3/FormBody.kt
} /** * Either writes this request to [sink] or measures its content length. We have one method * do double-duty to make sure the counting and content are consistent, particularly when it comes * to awkward operations like measuring the encoded length of header strings, or the * length-in-digits of an encoded integer. */ private fun writeOrCountBytes( sink: BufferedSink?, countBytes: Boolean, ): Long {
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Tue Jan 09 12:33:05 UTC 2024 - 4.3K bytes - Viewed (0) -
src/main/java/jcifs/smb1/netbios/NodeStatusResponse.java
private NbtAddress queryAddress; private int numberOfNames; private byte[] macAddress; private byte[] stats; NbtAddress[] addressArray; /* It is a little awkward but prudent to pass the quering address * so that it may be included in the list of results. IOW we do * not want to create a new NbtAddress object for this particular
Registered: Sun Nov 03 00:10:13 UTC 2024 - Last Modified: Fri Mar 22 20:39:42 UTC 2019 - 6K bytes - Viewed (0) -
src/main/java/jcifs/netbios/NodeStatusResponse.java
private NbtAddress queryAddress; private int numberOfNames; private byte[] macAddress; private byte[] stats; NbtAddress[] addressArray; /* * It is a little awkward but prudent to pass the quering address * so that it may be included in the list of results. IOW we do * not want to create a new NbtAddress object for this particular
Registered: Sun Nov 03 00:10:13 UTC 2024 - Last Modified: Sun Jul 01 13:12:10 UTC 2018 - 5.9K bytes - Viewed (0) -
mockwebserver/README.md
Because it exercises your full HTTP stack, you can be confident that you're testing everything. You can even copy & paste HTTP responses from your real web server to create representative test cases. Or test that your code survives in awkward-to-reproduce situations like 500 errors or slow-loading responses. ### Example Use MockWebServer the same way that you use mocking frameworks like [Mockito](https://github.com/mockito/mockito):
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Sun Dec 17 15:34:10 UTC 2023 - 5K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/http/HttpHeaders.kt
import okio.Buffer import okio.ByteString.Companion.encodeUtf8 private val QUOTED_STRING_DELIMITERS = "\"\\".encodeUtf8() private val TOKEN_DELIMITERS = "\t ,=".encodeUtf8() /** * Parse RFC 7235 challenges. This is awkward because we need to look ahead to know how to * interpret a token. * * For example, the first line has a parameter name/value pair and the second line has a single * token68: * * ```
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Mon Jan 08 01:13:22 UTC 2024 - 7.2K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/MultipartBody.kt
} /** * Either writes this request to [sink] or measures its content length. We have one method do * double-duty to make sure the counting and content are consistent, particularly when it comes * to awkward operations like measuring the encoded length of header strings, or the * length-in-digits of an encoded integer. */ @Throws(IOException::class) private fun writeOrCountBytes( sink: BufferedSink?,
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Mon Jan 08 01:13:22 UTC 2024 - 10.9K bytes - Viewed (0) -
architecture/standards/0006-use-of-provider-apis-in-gradle.md
} class Example { Property<NestedType> getNestedProperty() } ``` This is unnecessary because users will have trouble creating instances of `NestedType` and merging different instances of `NestedType`. It's also more awkward for users to access the properties in the nested property. If the nested type is a managed type (Gradle can generate its implementation), you can define a nested property with: ``` interface NestedType {
Registered: Wed Nov 06 11:36:14 UTC 2024 - Last Modified: Tue Oct 15 20:00:57 UTC 2024 - 10K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/primitives/ImmutableDoubleArrayTest.java
* Whenever an implementation uses `instanceof` on a parameter instance, the test has to know that * (so much for "black box") and try instances that both do and don't pass the check. The "don't" * half of that is more awkward to arrange... */ private static <T> Iterable<T> iterable(final Collection<T> collection) { // return collection::iterator; return new Iterable<T>() { @Override
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Oct 25 18:05:56 UTC 2024 - 21.2K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/primitives/ImmutableIntArrayTest.java
* Whenever an implementation uses `instanceof` on a parameter instance, the test has to know that * (so much for "black box") and try instances that both do and don't pass the check. The "don't" * half of that is more awkward to arrange... */ private static <T> Iterable<T> iterable(final Collection<T> collection) { // return collection::iterator; return new Iterable<T>() { @Override
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Oct 25 18:05:56 UTC 2024 - 20.1K bytes - Viewed (0) -
guava-tests/test/com/google/common/primitives/ImmutableDoubleArrayTest.java
* Whenever an implementation uses `instanceof` on a parameter instance, the test has to know that * (so much for "black box") and try instances that both do and don't pass the check. The "don't" * half of that is more awkward to arrange... */ private static <T> Iterable<T> iterable(final Collection<T> collection) { // return collection::iterator; return new Iterable<T>() { @Override
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Oct 25 18:05:56 UTC 2024 - 21.2K bytes - Viewed (0)