unstarred

After seeing this post, the malware devs may have unfollowed/unstarred the repos used in order to evade discovery.

The thought of somebody fucking with my unstarred, unfinished, unreadable learning project repos doesn't keep me up at night.

Starhub Notifier: Analytics about stars, release download count, who followed/unfollowed and starred/unstarred your Github repositories plus watch and notify by email.

Star-bellied Sneetches pay to be unstarred, and Plain-bellied Sneetches pay to get stars upon thars.

It seems there's no concrete example of where unstarred LET would be better.

The unstarred let is a destructuring bind of an entire tuple.

This was so incredibly annoying that I added this uBlock Origin filter: github.com##div.release >.body >.border-bottom.py-3.color-border-secondary.flex-items-baseline.d-flex Also, I unstarred pretty much everything.

So inline and all the \begin\ends, starred and unstarred.

If a programmer ever falls in the habit of sometimes using unstarred LET, then it's likely he'll make a mistake by using it where starred LET* was the right thing.

>It seems there's no concrete example of where unstarred LET would be better.

I nuke all unstarred msgs from mailing lists, etc.

>If a programmer ever falls in the habit of sometimes using unstarred LET, then it's likely he'll make a mistake by using it where starred LET* was the right thing.

On desktop gmail you can reproduce this functionality by starring messages you want to keep and then bulk selecting using the "unstarred" option.

I have a question, though: did you intend for people to frequently click "select unstarred" (or similar) and [archive] at the top to cull the list?

"0.07% of people use select unstarred", apparently.