klaim / arewemodulesyet

Are we modules yet? Not even close, lol.

This website will track the most popular c++ librarys, compiler and build system. We use vcpkg to get a rough idea on how popular a library is via how many revisions the port has. For more infromations, checkout the python script that parses the data generate_vcpkg_usage_stats.py.

Legend for progress_overwrite.yml

Example port

ports: 
- name: fmt
  # Unix timestamp, since when the lib has modules support. Used for extrapolating finish date
  modules_support_date: 1665476134 
  status: ✅
  help_wanted: ❌
  current_min_cpp_version: 11
  # These are often multiple issues, but always try to link the main issue
  tracking_issue: "https://github.com/fmtlib/fmt/pull/3134"

Note that most projects do not even have an issue for tracking modules support. If so you would have to create one, so we can track it here.

status

• ❔ Default: No set. Help wanted for every lib that has this status!
• ✅ Full support
• ⚠️ Corresponding tracking issue was closed and no planned support anytime soon.
• ❌ Not planned anytime soon.
• 🐌 Planned but no estimation. Ask again in like 5 years.
• 💀 Needs support old library/compiler/build tool to even start adding support for modules.
• 🤡 Maintainer does want to keep it oldschool. No plan to update anytime soon.
• 🪨 Is actually a c project so we will never see modules support, because c has no modules support.

help_wanted

• ✅ Yes
• ❌ No
• 💀 Does not allow outside contributions

Dependencies

1. Hugo
2. Python3 and the pip dependencies below.
3. Optional: Latest vcpkg

# Install python dependencies
pip install pyyaml gitpython termcolor
# Start local hugo
hugo serve
# Update your progress_overwrite.yml and genererate progress.yml
# hugo will then automatically refresh
python.exe .\generate_vcpkg_usage_stats.py --merge

Optionally rengerate raw_progress.yml

python.exe generate_vcpkg_usage_stats.py --repo_path=C:\vcpkg