You can spin up a single threaded runtime to perform these async calls without the need to "infect" the rest of the program.
The strategy is to spin up a single threaded async runtime and to just perform that call and block on the runtime itself. The easiest way to do that is probably https://github.com/zesterer/pollster
And there really isn't much in there so you didn't need to worry about performance or anything like that.
I recently refactored a colleague's program from async to sync because it's essentially and entirely sequential.
The reason it started its life as async was the reqwest library, which first and foremost provides async methods to perform http requests.
However, tucked away behind a feature flag aptly named `blocking` there is a small API that wraps the async api and allows making sync/blocking calls in a non-async main. And there they employ the same strategy of having a thin async runtime that blocks on completion of the async call.
Good. I swore to never get an LG phone again after my terrible customer service experience sending in my G4 for fixing their serial bootloop issue. Sent the phone in, took two weeks for it to get fixed, and then got lost on the way back to me. I then had to fight DHL to get some of my money back. Their customer service line threatened me with their legal department should I write about this online.
Having const generics will also permit much more elegant implementations of low level linear algebra.
For example, when writing a `GEMM` (general matrix multiplication) routine, the core building block is a so called kernel, which gets moved over the matrices like a stencil. The size of the kernel however depends on a) the numerical precision (float, double), b) the available SIMD intrinsics, and c) the architecture the code is executed on (haswell, skylake or zen have different latency and throughput for different intrinsics).
Right now it's surprisingly painful to write an optimal kernel and buffer, which is different for every architecture and which you need to kind of hardcode. With const generics this should become much easier.
I live in Germany, and I do compare salaries to American numbers. This is the very reason why I will never work for German companies ever again, because I'm not willing to be dependent on wage labour until the end of my days. I am working remotely for a US startup, who a) value my skillset instead of using antiquated tech, and b) who pay twice what I made before in Germany, and c) recently made me a cofounder.
German startups aside, our big multinationals happily create teams working in the the US and Germany, while paying their German employees a fraction of their American colleagues. I know of cases in pharma, automotive, and erp.
I'm loathe seeing this contentment with the wage situation in Germany. If wages for in demand fields like Software engineering are essentially flat for 30 years and €70k are considered an amazing salary, how exactly are wages supposed to rise in service sector fields, for example for caregivers? Salaries as part of gdp have deceased over that time range, but the prevalent ideology among my crowd is that one shall not work for money, because that's apparently a dirty thing to do.
Software engineers not pushing for significantly higher wages and gaslighting people who do makes them accomplices to the wage surpression that is rampant in Germany and the EU at large.
I try to completely avoid any synthetics and wish they were taxed into oblivion to account for externalities like polluting entire ecosystems.
Mind you, high quality synthetics are probably fine if you plan on wearing them for 20+ years.
What bothers/worries me is that fast fashion is pretty much entirely synthetics based and sells enormous quantities.