Readit NewsReal wisdom is to know when to show empathy and when not to by exploiting (?) existing relationships.
Current generation of LLM can't do that's because every they don't have real memory
And I especially don’t buy that UB is there for register allocation.
First of all, that argument only explains UB of OOB memory accesses at best.
Second, you could define the meaning of OOB by just saying “pointers are integers” and then further state that nonescaping locals don’t get addresses. Many ways you could specify that, if you cared badly enough. My favorite way to do it involves saying that pointers to locals are lazy thunks that create addresses on demand.
It explains many loop-unroll and integer overflow as well.
When you decouple the language from the hardware and you don't specify an abstraction model (like java vm do), "the platform" is just whatever the implementer feels like at that moment.
I think this is just wrong. The number of download does not reflect how important or impactful a report is.
If you used uncommon colors in your program on - for example - a Sparcstation 20, the palette would shift every time you moved the mouse in or out of your window. It's difficult to describe to someone that's never seen it, but it's unpleasant. No one mourns the death of pseudocolor.
--
Passkey - what would happens when we lost the device? You need some kind of recovery, right?
Social recovery - of course you could do that. Are you doing one recovery for all accounts (which require some kind of "wallet" stored in a centralized location - and can be disabled)? Or one for each services (which may make your grinder account known to your family)?
How about tourists? When you lost your phone while you are traveling in other country, what should you do?
--