GitHub 火线榜

GitHub 火线榜 · 仓库档案

jpakkane/pystd

A self-written C++ standard library (简介来自仓库自身文档。)

数据截至 10月26日jpakkane

最好成绩

#230

被忽视榜 · 活跃却无人问津

100

累计 Star

1

Fork 总数

2

近 30 天在榜天数

项目状态许可证: NOASSERTION最近 push: 10月19日Open Issues(含 PR): 1

自 2026-10-25 起采集;未知 = 尚未采集到

把上榜徽章放进你的 README · jpakkane/pystd[![把上榜徽章放进你的 README](https://git.vaiox.xyz/api/badge/jpakkane/pystd.svg)](https://git.vaiox.xyz/zh/repo/jpakkane/pystd)
<a href="https://git.vaiox.xyz/zh/repo/jpakkane/pystd"><img src="https://git.vaiox.xyz/api/badge/jpakkane/pystd.svg" alt="把上榜徽章放进你的 README" height="20"></a>

项目文档

A self-written C++ standard library

Design goals:

  • NOT an implementation of the ISO C++ standard library, but instead an experiment to see what a stdlib without backwards compatibility requirements might look like
  • design-wise copy the Python standard library's APIs whenever possible
  • minimize build times
  • a single header for the most common things
  • KISS
  • needs to be performant, but not "super optimized" to the hilt
  • Can use existing C libraries like pcre but not C++ libraries

API and ABI stability

Do both of these:

  • Maintain perfect API and ABI compatibility
  • Make it possible to change both in arbitrary ways

This seems impossible but is in fact fairly easily achievable:

  • Put everything under pystd<year> namespace

  • When release happens, copy all files from foo<year>.[ch]pp to foo<year+1>.[ch]pp and rename the namespace accordingly

  • The old version remains forever frozen in time

  • Arbitrary changes can be done to the new version

Anyone who needs to interoperate with code using the old versions can #include the old header and use things from its namespace as needed.

Limitations

Tested with GCC and Clang on Linux and macOS. Does not work with MSVC as it has not yet added support for pack indexing.

当前上榜

  • 230

    被忽视榜 · 活跃却无人问津

    100 星 · 1 fork · 累计 Star(升序)

    被忽视 →

近 30 天势头

累计 Star 走势

名次走势

同榜竞速 · 名次近邻 · 被忽视

← 回到榜单