The standard only allows reading a value as the type it was written with or as char, and an access as char is only good for copying. If a char access used different bit order, that would be OK according to the standard because you couldn't tell unless you violated the standard.
It seems every compiler will tolerate a memcpy for type punning, even though this isn't required.
The only real solution to gerrymandering is to use a minimally-complicated algorithm.
The algorithm need not actually determine the districts. It can instead simply rate proposals, allowing a contest to be held. The highest scoring proposal submitted at least 400 days prior to the election is the winner, with earlier submissions winning any ties.
Another improvement would be to let districts spill over state borders. One could exempt Alaska and Hawaii of course.
I found the comment to be insightful. I'm trying to find his violation, and I can't really. There are a few things that are close, maybe, but not really.
"political or ideological battle" and "shallow dismissals" seem most plausible, but neither really fits. It's not as if the entirety of his comment was "more dumb leftist shit". There was more substance to his comment.
Ah, but why were there children and old people being murdered en masse?
It's because humans naturally resist what was being imposed upon them. The smart and able-bodied are going to get more, and they will resist any effort to prevent this. Corruption and workplace theft were rampant in the Soviet Union.
IDA Pro is far more usable, particularly for heavy-duty long-term users. There is a bit of a learning curve, but IDA Pro has a really efficient interface. You get the beauty and readability and nice flowchart-like layout that can be done in a GUI, while the keyboard control has efficiency like a well-made DOS or mainframe program.
The politician pays the union. The union pays the politician.
So both are getting paid, out of money taken by force from the population. Neither has an interest in making this stop.
About the only hope is that 1-sided political donations will sufficiently tick off a political party at the national level. There is a tiny chance that national law could change because of that.
You also have two parties, the "government" and the "opposition". They are created after the election. At that point, the voters no longer get any say. The voters don't even know what they will get.
Consider a situation that starts with 12 parties. One gets 45% support, and the others each get 5% support. When the 12 parties merge into the 2 that will actually govern, that party with 45% may be the loser. The other 11 can merge to become a party with 55% of the power. The party which is most popular by far is thus locked out of power.
Numerous states had already sued the Obama administration in the other direction. (DACA being unlawful in the first place) Due to those still-ongoing lawsuits, DACA was probably about to go down in flames already.
The sea salt craze has always seemed odd to me. Have most people in the USA never been to a beach? Do people really think that the sea is a good source of salt?
What I associate with the sea: seagull droppings, rotten seaweed, spilled oil, dumped WWII chemical weapons, raw sewage...
Then I go to the store and see a box of Triscuit crackers featuring sea salt. Yum??????
How much job capacity do you personally need? Isn't it enough to have just one job? Many cities have that and more, and it only takes one job to support a family.
I hope you don't expect to lose your job every few months, but in case you do, remember that new jobs pop into existence. It's not like a city with 100 jobs is on the verge of running out. (several years later: "oops, the last job got used up in 2018 and we can't ever make any more; this city is all used up")
I've had my tech job for a dozen years now. It pays well enough to get a 3500-square-foot house on half an acre and feed a huge family, even though the pay is perhaps only 2/3 of what I'd make in San Francisco or Mountain View. The 5x to 10x difference in housing cost more than makes up for the salary difference.
Leave a car for months, and you'll get back to a dead battery. Keyless entry won't work. You can't roll down the windows. Settings may be forgotten. There is no way to start the engine.
Leave a car out in the Sun in a place like Arizona, and stuff melts. If you get in the car, the seatbelts cause burns that blister. Having the car run a fan would be nice, and the more you need it the more power there is available to do so.
You say that Zig has no macros, just like FORTRAN, but that isn't a language property at all. Technically, C has no macros, but most people use the C preprocessor. I've seen people preprocess with sed scripts, perl scripts, tr, python scripts, and m4. FORTRAN too was often preprocessed.
So we'll take your Zig and shove it through a preprocessor or several. I've seen code get preprocessed 3 times during builds, but I'm sure that isn't a record.
If a language designer fails to provide a suitable well-matched and effective preprocessor, we'll add something nasty. Oh well. Stuff has to get done.
That is way too dismissive, wrongly comparing total cyclone energy with what we can generate.
A more reasonable objection would be that we don't desire a radioactive cyclone. This is an obvious downside, though there are low-fallout designs (most energy from fusion) that aren't too bad. We did survive the 1960s after all.
We'd have to simulate and test many times. Better prediction capability, for both cyclones and nukes, would increase the chance of knowing if we made a difference.
Nukes might not be the best way. Silver nitrate cloud seeding was tried in the 1950s, but we can't know if it actually made a difference because we didn't have much ability to predict things back then. (wimpy computers) Another approach is to block ocean evaporation. Create an oil slick as large as the cyclone, and there you go.
Maybe we need all three at once: oil slick to weaken it, then nukes and silver nitrate to steer it. Note that this would likely be an operation that puts the Berlin airlift to shame.
The standard only allows reading a value as the type it was written with or as char, and an access as char is only good for copying. If a char access used different bit order, that would be OK according to the standard because you couldn't tell unless you violated the standard.
It seems every compiler will tolerate a memcpy for type punning, even though this isn't required.