>Rather, it only checks for method names and where-clauses such as T: Trait. Types are only resolved in the confirm phase, at which point rustc would have already picked its method.
Not following here, the compiler iterates over the deref-chain and acquires a list of method names, but it also "checks for ... where-clauses", what does that mean? A quick look at the linked probe code indicates what we filter on Self traits and return value traits.
>I see words like “flakes” and “derivations,” and I currently don’t know what they mean.
>So far, I don’t get how it’s deterministic.
To make nix deterministic you can specify a hash in non-flakes (or a git rev) for your dependencies, but flakes make this easier. When you "run" a flake (be it nix build, nix shell, nix develop), nix pulls the latest (if no explicit rev given in the flake.nix already) version of whatever is specified in flake.nix that it can find, and creates a `flake.lock` file that specifies the exact version that was used. This file is very similar to cargo's Cargo.lock, and specifies the exact version that was captured by ref/hash. The next time nix is "run", it uses the lock file to get the exact same version as it had previously.
One can develop a flake.nix locally, install, check if everything works, and alternatively change the refs in the lock file to make everything work. When this is done you can move the nix and lock file to another machine and get the same exact build there (with the exception of architecture differences).
Because you can put flake.nix and flake.lock inside of git, you can also share the exact same dependencies with other people using a repository. Whenever I see a repository using these I know that building will be a breeze because I don't have to do any dependency hunting.
>I don't have any particular answers to why string templating has been enduringly popular so far (although I can come up with theories, including that string templating is naturally reusable to other contexts, such as plain text).
Clicked on that expecting it to be an article about how corsets remained popular with women in the Victorian and Edwardian eras even as doctors kept recommending against them.
Perhaps it's the same advantage of living in a society like ants or humans. By keeping each other alive we stand stronger against other forces of nature and/or other species of trees or plants.
Germany, for sure - tenants usually own their own washing machines and most of the time, their own kitchens, including all appliances, cabinets and the proverbial kitchen sink. Tenants are essentially paying for the right to occupy the dwelling, and that’s about it.
Therefore rental price to purchase price ratios have historically been lower, as well as home ownership rates. Rents in desirable cities are going up faster than they had been, though, and Berlin has quickly gone from being one of the cheapest cities in the country to one of the most expensive.
In Eastern Europe it's often the case. Worth mentioning however that plumbing services are much cheaper then in States, and there are usually no legal/insurance nuances which reapairing may bring in the US. So it's simply easier to call a plumber and have trouble solved then include a landlord into equation. Broken washing machine, or expensive furniture in most cases are on landlord, though.
Not following here, the compiler iterates over the deref-chain and acquires a list of method names, but it also "checks for ... where-clauses", what does that mean? A quick look at the linked probe code indicates what we filter on Self traits and return value traits.