I just went through that recently, chat bot responded instantly to the mail with the same reply as the FAQ help, then the human responded after an hour asking for screenshots to see that showed I actually tried, then after a day an engineer fixed it.
Ugh... and don't even get my started about the pronunciation of "Azure" (or the fact that, somehow, they took a project code-named "Red Dog" and named it after the color blue. Then there's the JEt Red and Jet Blue database engines, one of which was used by Active Directory...)
You're forgetting Azure Active Directory Domain Services, which is presumably now named Entra AD Domain Services which is different from Azure AD/Entra AD because it's a managed domain controller in Azure...
Not the person you are asking, but I do have GI issues due to the acidity with coffee. It can cause reflux, ulcers, and more for people if they are sensitive to the added acidity.
Not for me, but it is for some people. My current issue is more esophageal, my throat gets inflamed with too much acid then it feels like I have food stuck and can’t swallow it. Other people have stomach issues, ulcers, etc. but still want to enjoy coffee, so I think there’s plenty of reasons for cold brew served hot to exist.
> Let exceptions propagate, catching them at as high a level as possible.
This can't be done cleanly in Java.
Checked exception can encode union types, but this extra power is not complemented anywhere else in Java's type system.
E.g. in a `Consumer` lambda passed to `forEach`, Java's checked exception forces you to convert that to a RuntimeException.
I'd say it is due to a lack of variadic type parameters. You can write something like this:
<T, X extends Throwable> void forEach(ThrowingConsumer<T, X> f) throws X;
But the only way to have multiple exception types without losing static type checking is to have multiple X parameters, like X1, X2, X3... (with unused parameters being set to some subtype of RuntimeException so that they do not participate in checked exception handling).
Whether or not it is worth to write this madness just to satisfy one's OCD is up to the reader.
To be pedantic, it is due to union types "not complemented anywhere else in Java's type system". Adding variadic type params is a way to solve this. Another way is, of course, to support union types.
> with unused parameters being set to some subtype of RuntimeException
Or the `Nothing` type (`never` in TypeScript), where `A | Nothing = A`.
https://news.ycombinator.com/item?id=40307098
> Inspired by datatype99, but consisting of one small standard-conforming C99 macro-only header that is fast to compile.
reply