On Thu, 4 Mar 2021 12:16:29 GMT, Сергей Цыпанов
wrote:
> When we do
> byte b1 = (byte) (value & 0xFF);
> we keep from int only 1 lower byte and exactly the same can be achieved with
> plain cast. See the test below:
> public class Main {
> public static void main(String[] args) throws Excepti
> On 13. Jan 2021, at 17:50, Daniel Fuchs wrote:
>
> [...]
> It's not clear to me whether NFC should be applied - or what would be
> the consequences of applying NFC there (or not).
While I can't answer this question, it may be worth mentioning RFC 3987 which
might not be directly applicable
Hi all,
I just stumbled upon a strange behaviour and I'm not sure if it is intended
this way or whether it's a bug. It is also possible I'm using the API
incorrectly. Let me explain with an example:
```
var originalException = new Exception("foo");
CompletableFuture.failedFuture(originalExcepti
Certain users of my software run into problems with HttpClient.newHttpClient()
on JDK 14.0.1 and I don't feel like I can handle it properly without catching
Errors.
Calling said method fails when encountering Selector.open(), which in its
Windows-specific implementation relies on loopback-TCP c
Certain users of my software run into problems with HttpClient.newHttpClient()
on JDK 14.0.1 and I don't feel like I can handle it properly without catching
Errors.
Calling said method fails when encountering Selector.open(), which in its
Windows-specific implementation relies on loopback-TCP c
