I realize that speeding up Java's base64 w/ SIMD probably has a measurable impact on a significant proportion of all webservers everywhere. But at the same time, implementing the entire thing in ASM, by hand, looks ... rough. Here's the comment describing how it works:
Because sometimes you just want to talk about the types of variants without having to construct a value. But, you probably don't want to manually maintain a separate enum just for the discriminants. Nor do you want to manually maintain the mappings between the original enum and the discriminant-only enum.
I've had it come up when dealing with ASTs, although I don't recall the specifics. This is a problem that's certainly pretty easy to solve with macros. I'm pretty sure last time I ran into this I used `strum` [1] and its `EnumDiscriminants` macro to handle this.
Very, very much yes. Most busy airports will start having problems with gate capacity due to just normal delays. We definitely don't have the capacity to have every active flight in the country parked at a gate.
I wrote code (I am old) before stack overflow. Google existed, and it was even still in the honeymoon phase where "don't be evil" was almost plausible. But search engines were not yet a good tool for solving esoteric programming questions.
But honestly, the practice of programming then was not dramatically different from programming in, say, the mid-2010s. Obviously we leaned more heavily on the official documentation, and tbf, a lot of the docs were provided in PDFs, which is probably the single worst way to provide documentation.
Sometimes, the docs were provided as collections of papers bound together by a "spine". This is actually a wonderful documentation format because our brains can associate physical locations in the physical media with specific pieces of information.
(this is the oldest I have ever been in my entire life)
https://github.com/openjdk/jdk/blob/5177a70b385c16f26ede191f...
reply