tyler569

Without being a domain expert, my intuition would be that PCIe is optimized for throughput over latency and there's probably a throughput compromise when you want low-latency access.

The best part about using nuclear for fuel generation is that you get to sidestep the biggest problem with nuclear - when you build a power plant you want to build it near people (who may object on safety grounds), but you can build a DAC fuel generator way out in the middle of nowhere.

Even better, you could build your nuclear DAC fuel generator in an old natural gas field, where there's ready-made transportation infrastructure for your product to where it's needed!

This sounds to me like someone put in real UV fluorescent tubes instead of blacklight tubes, those things are dangerous.

And that ABI specific stack manipulation would be UB, so the optimizer can assume it doesn't happen. With no UB, that's not true.

The accepted proposal does address and preserve `auto`'s use as a storage class, so `auto x = foo(y);` means type deduction based on the return type of `foo`, and `auto int x = 10;` declares an integer with automatic storage duration.

Git does have tools that allow you to rewrite history to fix situations like this, but by far the easiest solution is to invalidate those credentials so they become worthless.

Interesting that your employer would be so zealous about it, my employer's written policy is "Always cooperate with security/customs. If they want your computer unlocked, unlock it. Your safety is more important than our secrets, just call corporate security when you're released."

Probably a lot like https://github.com/PowerNex/PowerNex :)