3,522 karma · joined February 4, 2014
I won't get into the HTML part (I think it's obvious), but the
$(|_e| count.increment())
part is a rust closure. |_e| is the argument to the closure, which has a leading underscore because it's unused. I imagine it's some context about the event (thus the e).
The rest is the body of the closure. It increments the count.pretty simply
enum Value {
Float(f64),
Ptr(*const T),
}
Do you want the compiler to disallow certain bit patterns in the Float variant simply so that it can implement NanBoxing?To argue with your actual point: I don't really care about the overall context, actively disallowing tests in a codebase is a _bad decision_. Look how it worked out for them.
> it's time for you and I to bug out conversationally
Fine with me
I got the sense from your reply that some extra clarity would be beneficial.
> This is unnecessary. OP came out with "AUTHOR IS INSANE" even on the most generous of interpretations.
I did not actually call the author insane, I called their decision to explicitly disallow testing insane. It's an insane decision. I am not _literally_ calling the author insane.
I did not.
There is no ability here for the cost benefit analysis to change over time. There is only no tests
Perhaps more unsurprisingly, at the mere suggestion that socializing is good for you (it demonstrably is https://pmc.ncbi.nlm.nih.gov/articles/PMC11403199/), you went and wrote a comment that I can only imagine someone who is deeply unhappy would write.
I know what ECDSA is and if you brought it up in a random conversation unprompted I'd try to find your spaceship so I could escape the conversation on it.
But beyond that the thing I don't understand about the modern hate towards macros is that they are simply very fun.