> Using Vec for arrays is also annoying, repeating the mistake from C++.
Neither Rust nor C++ uses vectors as array, they're distinct things.
An array is a fixed-size object, which never allocates and its elements thus always retain their memory address. In Rust they're `[T; N]`, in C++ `T[N]` or more recently `std::array<T, N>`.
A vector on the other hand is dynamically sized object, that may (re)allocate to accomodate new elements, and the address of their elements can change. In Rust they're `Vec<T>`; in C++ `std::vector<T>`.
I'm aware of how they are used, but fundamentally there is nothing with the words "array" and "vector" that says that one has a fixed size and the other has a dynamic size. If anything, it should be the other way around. Using the name vector for dynamic arrays is annoying when doing any kind of math coding. Even the designer of STL says the name was a mistake.
Apt has just 3 listed maintainers, and judging by the git history this guy does 90% of the work. Him making the decision _is_ it happening organically.
Open source fundamentally is a do-ocracy (it's in literally all of the licenses). Those who do, decide; and more and more often those who do are just one or two people for a tool used by millions.
The only spec you need meet to get Perl or Python running on a new platform is the C spec. A compiler meeting that spec is enough to port and compile the interpreter for a new platform.
> Furthermore, if these architectures are removed from further debian updates now, is there any indication that, once there's a rust toolchain supporting them, getting them back into modern debian wouldn't be a bureaucratic nightmare?
These architectures aren't being removed from Debian proper now, they already were removed more than a decade ago. This does not change anything about their status nor their ability to get back into Debian proper, which had already practically vanished.
Even if technically possible, it's unlikely this will be used to support any of the variants you mentioned in Debian. Both i386 and armel are effectively dead: i386 is reduced to a partial architecture only for backwards compatibility reasons, and armel has been removed entirely from development of the next release.
What you said is correct wrt. official support, but Debian also has an unofficial ports infrastructure that could be repurposed towards enabling Debian for older architecture variants.
Yes, depending on your highlighting scheme. Not every highlighting scheme shows this by default, unfortunately.
To me, this seems initially like some very minor thing, but I find this very helpful working with non-trivial code. For larger methods you can directly discern whether a not-as-immutable-declared variable behaves immutable nonetheless.
> I assume this is an entirely independent Chinese company without some Dutch sponsor or something.
It's not, it's a Dutch company, formed according to Dutch law, with headquarters in the Netherlands, that was bought by another Chinese company a few years ago.
Dutch law sets rules on how any company, but especially public companies (so-called naamloze vennootschappen) must be governed. Even if you own all the shares, by law you don't have unlimited and unchecked power in the company, you have to abide by governance rules.
Seemingly simultaneously with the government order, a suit was brought to the court enforcing these laws (the Ondernemingskamer) alledging that the CEO and owner were not abiding by them. The court documents are a bit weird to me as a non-lawyer, with Nexperia named as both plaintiff and defendant, so I'm not sure who brought it, but it might've been the government, who are named as a party.
The court agreed that the suit could have merit, and as an interim measure while the legal proceedings play out, has suspended the CEO and named a temporary director. It also suspended the authority of the owners over their shares (except for one), and assigned a trustee to manage them temporarily. The court did not actually rule on the contents of the suit yet, it only issued interim conservatory measures. We'll likely hear more about how the suit plays out over the next few months.
An interesting matter of contention in the suit is that the CEO/owner want the CLO to be suspended, while the other side asks the court to prohibit firing of the CLO. I presume there has been a conflict in the board, either leading to or caused by the government order.
Sounds like the OR (ondernemingsraad) apparently wants to get rid of the CEO for incompetence which is very interesting. It is extremely hard to prove (in a court of law) but a valid reason. I assume they were doing all kind of shady things if they go that route. (Havent read the Court Docs, it is a guess)
OR vs CEO also explains the duplicate entries as they are both representatives of the company.
It is, if anything, anti-functional: unless it smothers everything the litter provides nitrogen and nutrients as it decomposes.
Getting rid of all the litter for that “perfect lawn” requires re-introducing nitrogen artificially (historically lawns would be grown with clover, the clover being a nitrogen fixer for the grass, that stopped being a thing when people started widely applying broad-leaf herbicides like 2,4D, the lawn industry then labelled clover a weed to make killing it a goal rather than a negative side effect).
100%, like cutting grass, all the stuff you cut and move out of your lawn is nutrients leaving your soil, do that long enough and you'll get dead soil, then you'll need to buy compost... which is made from the leaves, grass cuts and bio trash that you city charges you to collect. It's a perfect cycle really.
> the lawn industry then labelled clover a weed to make killing it a goal rather than a negative side effect
People who are into bio gardening/farming use cover crops to boost soil fertility and avoid weeds, very often clovers actually. You can even use them as cover crops while growing other things, again to compete with weeds, every know and then you cut them down, leave them on the spot, they decompose and feed your crops/earthworms
When we bought our house about 7 years ago, the lawn was in terrible shape. I’m not a huge fan of lawns—-I’ve been slowly converting it to a garden—-but my wife likes one. Instead of going chemlawn like many of our neighbors, instead we started planting clover. This horrified my father in law, who spends inordinate amounts of time removing clover and dandelions from his lawn. Anyway, after years of planting clover and the occasional overseeding with grass seed in the fall, our lawn now looks very nice. And it stays nice even during drought (like right now). We also just mulch all the fallen leaves with a mulching blade on our lawnmower. So much easier than picking up the leaves, and you can barely tell that I did not rake them. Admittedly the lawn is not 100% grass, but who cares? This is not a golf course.
Before the spread of broad-leaf herbicides and fertilisers it was just normal, you’d get clover mix at the grower or lawn care shop or your lawn seeds would come with some amount of clover mixed in.
Neither Rust nor C++ uses vectors as array, they're distinct things.
An array is a fixed-size object, which never allocates and its elements thus always retain their memory address. In Rust they're `[T; N]`, in C++ `T[N]` or more recently `std::array<T, N>`.
A vector on the other hand is dynamically sized object, that may (re)allocate to accomodate new elements, and the address of their elements can change. In Rust they're `Vec<T>`; in C++ `std::vector<T>`.
reply