Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
Scan pending.
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
> What's so bad about it? I wouldn't use the word bad. It suggests that there is something objectively wrong with it, which I don't think it is. I encountered @This at the top-level while reading a PostgreSQL protocol implementation (e.j. here and here). My understanding is that it is used when using the whole module as a struct ([reference])? That means that a file/module is a struct? Can a module be instantiated multiple times or is it a singleton? Currently I think the answer is multiple times. Again there is nothing wrong with it, Perl's moose takes a similar approach of a module/file being the class itself. In general I don't like designs that favor creating several files when one would suffice. [reference]: ziglang.org