User: Be offensive!
LLM: *Is offensive*
Social media: OMG how could this happen?!?!? Why didn't Elon stop it?!?1,260 karma · joined July 5, 2017
User: Be offensive!
LLM: *Is offensive*
Social media: OMG how could this happen?!?!? Why didn't Elon stop it?!?e.g. from the playground: `static const uint64_t MERSENNE_PRIME = (1ULL << 127) - 1;` which it insists is the correct way to store a 128-bit integer in followup questions.
The theoretical idea is that the information could be hidden in a random location, e.g. extracting every Nth bit, such that the information would be indistinguishable from random noise. In practice, both parties need to agree on the location, so it has the same flaw as 'perfect encryption' methods like a one-time-pad, you need to transfer information IRL.
One could make a case for a group/app using a custom scheme to add a layer of security until someone infiltrates the group / RE the app, but you'd get the same security by just encrypting everything with the same password.
Sidenote, look up the ThinkPad 760 series, it had some really cool features. Raise-able keyboard so you could have it at an angle, physical sliders for sound and backlight, easy access to the internals and hot-swappable battery.
> What features were added in C++ 98?
< C++98 (also known as C++11) was a major development milestone for C++
< new gcc 5.1 standard, which was the first version of the standard to include support for AES encryption
< return types and various other changes
> Write a C++ constexpr function that implements powf
< Sure! Here is an implementation of a C++11 constexpr function for the function pow, using C++11 recursion and variadic templates:
< void pow (int n) { std::cout << "Powerset of " << n << " is " << pow (n, n) << std::endl; }
< This implementation of the pow function should be possible for any constant integer power of 2 without exception.The only reason I can see is lowering the overhead of creating threads, at the cost of harder to read controlflow.
Except when they booted sites off their network because Twitter users were upset..
There's a few valid 16 byte instructions though.. Sandpile lists a few examples: https://www.sandpile.org/x86/opc_enc.htm
36 67 8F EA 78 10 84 24 disp32 imm32 = bextr eax,[ss:esp*1+disp32],imm32
64 67 8F EA F8 10 84 18 disp32 imm32 = bextr rax,[fs:eax+ebx+disp32],imm32