ks6g10

Fair.

Hopefully we will get P1729R5 in 29.

But then input handling is much more complex than output handling.

Also, 26 now initialises trivial variables with erroneous values, and is no longer undefined behaviour to act on them.

From colleagues in various national bodies, it's very political since it's about "taste" for various features rather than e.g. bug fix in the standard which is fundamentally neutral.

Would myself (not in the committee) argue that contracts as is would most probably be relegated to modules support hell in terms of support and implementation variations, and I think it's in everyone's interest not to repeat that.

The fact that contracts allow non pure functions to be called is just begging to be a large source of bugs to be. I think that if they started with pure functions, then in future standards mechanised some way to call non pure functions? Would be better and more accepted.

Just like reflection, instead of being overly encompassing, we were given at least the beginning to something great. (Though I dislike some syntax and utility functions, as well as the bareness of some reflection, e.g. can't reflect on templates, other than is it a template.)

Normal Plex works using that way, so probably.

Not OP but have been in same boat, stage 4 bowel cancer.

My first symptom I noticed was consistent blood on stool, still remember that day I first noticed it.

That was later followed by stomach cramps (obstruction) and night sweats (the stage 4 part).

Remember, cancer does not wait, get it checked if you notice anything out of the ordinary.

I would guess the roundtrip of intercepting every file stat call in the repo, it's very lovely. But will check.

For me it can be slow, especially refreshing magit (which probably is blocked by git, blocked by the bs)(on MacOS)

Even just rebase fixup a commit that is a few commits below HEAD is just a few chords away. Use it many times a week when working.

They should name it Multiple memory data, one single CPU instruction, or mmdosci for short. Easy to remember.

I scheduled my intune upgrade when I needed a week off for doing house moving stuff. I was told Emacs would work, didn't. Took them about a week before I could use it again.

But what is the resulting assembly? I would assume completely different!

Unfortunately some exchanges (twse) uses packed BCD encoding.

Just like 2 threads can execute on the same core at the "same" time, i.e. no synchronization, the same is true for GPU threads/ thread groups.

I just use tailscale and remote desktop.