#cpp17
Live, measured metrics for the hashtag #cpp17 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cpp17
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 09:33 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 09:33 UTCNo related tags with measured usage found for #cpp17.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:33 UTCEverything below is measured over the latest 40 public posts (spanning ~9898 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (36) · Arabic (2)
Avg boosts / post: 0.6
Top of the latest posts
Finally introduced a converting constructor for C++11 in my take of (nonstd) variant with its idiosyncratic typelist to support C++98. Hope to release v3.0.0 'really soon'. Back to the future or something :) #cpp #cpp98 #cpp11 #cpp17 https:
Anyone know the details on try-catch blocks in C++17 on Linux? Assuming that the normal code path throws zero exceptions, is it correct to think that there is no overhead in having try {}? That the overhead is only in the catch {} when an e
Today I share my lesson learned when it comes to structured bindings and a custom get in my post, "Something you should know about structured bindings" https://andreasfertig.com/blog/2021/03/something-you-should-know-about-structured-bindin
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/cpp17