That's the any type and the moving logic into json loaded at runtime features

Not really, the `any` type doesn't let you perform any operation on it with runtime dispatch like dynamic typing does. Moving logic into json isn't a language feature.

This only holds if society manages to hang together, which in the age of military strategy written by AI is looking borderline.

It won't last. You need a good grade to find work after so handing out lower grades decreases applications next year.

On the plus side, high grade + long ago remains a signal.

I doubt that's the bottleneck. UCB's acceptance rate is not high (<5% for CS). They have way more people who want to get in -- qualified kids, too! -- than they can fit. They'd need to burn through that backlog before it started showing up as a signal.

> high grade + long ago remains a signal

Does it? I didn't think people looked at GPAs once you're 5 or so years into a career.

Scale is a cuda implementation running on nvidia or amdgpu. Think nvcc semantics with template diagnostics by clang.

Nvidia including Spectral in their inception programs seems a big deal to me. It bodes well for the future of the cuda ecosystem.

If you'd like to run it, docs and download at https://scale-lang.com/. It's a clang fork with a bunch of libraries packaged. I'm on the dev team and always happy to hear from people.

Not imaginary. Eliding checks on nullptr and integer overflow were both implemented, shipped, miscompiled the linux kernel and grew flags to disable them. I expect there are more if one goes looking.

Well yeah that just means some aspects of the imaginary compiler were in some configurations approximated by some historical compiler versions and were in some cases rejected by the community (which cares about sane semantics even for behavior left undefined by ANSI/ISO) and in some cases left in as defaults but made trivially configurable for anyone who wants to define the undefined behavior.

Well, you can't write malloc in conforming C, which hurts rather more than remembering to write bitcast as memcpy on char pointers.

Doesn't matter though because you aren't writing standards conforming C. You're writing whatever dialect your compilers support, and that's probably (module bugs) much better behaved than the spec suggests.

Or you're writing C++ and way more exposed to the adversarial-and-benevolent compiler experience.

The type aliasing rules are the only ones that routinely cause me much annoyance in C and there's always a workaround, whether if it's the launder intrinsic used to implement C++, the may_alias attribute or in extremis dropping into asm. So they're a nuisance not a blocker.

I think large proofs done by humans also require hours of verification by other mathematicians, checking for "bugs" in a sense. I don't think they're obviously correct, I think it's like more like doing a code review.

I found a 5gbe one that claimed 60W, will power a phone but not the low power laptop I've got here. It probably isn't far off.

Ymmv. I've got a mix of cheap premade patch cables and some I crimped from solid core, all cat5e, all holding 10gbe totally happily. I suspect that only works because they're a meter or two long but that reaches across the rack.

It would do nothing. You'd get an increase in derivatives volume with the same underlying effect.