@_CJPROS I’ve tried this and can confirm it’s not worth it at all, no matter how dry you make it. The best part about scrambled eggs is that it’s not a paste
@trentengland@land10k_gophers At the basic level, you must resolve the question “do the people elect the president, or do the states elect the president?” I’m not arguing that the EC is unconstitutional, I just believe the current treatment of presidential elections in the constitution is outdated and wrong.
@trentengland@land10k_gophers That’s exactly what I said, NPV is not proportional to the total population, only within each state. It still has the issue that states have an unequal share of the electoral college.
@trentengland@land10k_gophers That has nothing to do with what I said. The EC is not equivalent to Parliament, it’s just a stand-in for apportioned voting for a position that shouldn’t be considered apportioned by the states. I fundamentally disagree with your premise.
@parcprinter@gooficat@vyrotek@Vision I’m not a huge fan of the double colon, I just want people to see the reasoning for it! Before Rust, I had to work with some files from a DSL config language where :: was syntactically equivalent to a space, so I got very used to it there (to my chagrin)
@FS_Grimm Changing the accessory depending on whether or not it’s a pointer is the silly part. If all accessors were arrows, fine, but that’s not how the language is written. I like arrows, Rust uses them for return types, I just don’t like how they’re used in C++.
@trentengland@land10k_gophers The EC was designed to make it so that the people couldn’t just elect a populist despot, not so candidates would have to visit swing states. Eliminating it means a candidate would have to appeal to the whole country rather than the special interests of each swing state.
@trentengland@land10k_gophers The NPV compact doesn’t eliminate the electoral college. States already have the constitutional power to decide how electors are appointed, NPV is just a compact to make it proportional to each state’s popular vote. It doesn’t even correct the apportionment issues.
@MudideShiva Lmao weird but yes it does feel like that. I’m just trying to imagine how you prompt an LLM to find these problems, like “go through OEIS (all of them) and find sequences where the next term isn’t obvious but could be calculated on a modern computer”
@MudideShiva Some of their “discoveries” look…correct, but none are particularly interesting. This one seems like very low-hanging fruit that nobody cares about, which makes sense because the founders seem to think OEIS sequence stop “when the next term is out of reach”
@gooficat@vyrotek@Vision I mean that you would have the same character being used for two different things. This is really confusing in trait bounds:
fn process<T: Iterator<Item = U:Item>, U: Iterator>(iter: T) {}
Obviously the compiler could distinguish all cases, there’s no need for ::
@trentengland@land10k_gophers Nothing you said depends on the EC though. With the popular vote, you still have to visit other parts of the country and draw wide support. With the EC, a couple of swing states define that support, presidents don’t campaign in states they know they’ll lose. That can change.
@vyrotek@Vision That interferes with the syntax for types. I mean you could, you could also use->arrows, wouldn’t that be ugly, imagine if a programming language did that
Steady progress on https://t.co/R9akzQKEN6
slowed down a bit due to new baby, but I'm picking back up
Down to 55 PRs, 26 issues now
Many improvements and fixes! If you post an issue I _will_ review it and if it makes sense & I can repro I _will_ fix it!
@120proofBrandy@CynicalPublius Except the electoral college neither gives states nor citizens of those states equal voting power based on their population or lack thereof. Apportionment is always unfair to some states and favors others. Your vote shouldn’t count for less if you live in Texas.