GitHub Hot Board

GitHub Hot Board · 저장소 아카이브

jpakkane/pystd

A self-written C++ standard library (소개는 저장소 자체 문서에서 왔습니다.)

데이터 기준 October 25jpakkane

최고 순위

#230

과소평가 · 활발한데 무명

100

누적 스타

1

포크 수

2

최근 30일 기록 일수

프로젝트 상태라이선스: NOASSERTION최근 push: October 19열린 이슈(PR 포함): 1

2026-10-25부터 수집. 미확인 = 아직 미수집

README에 뱃지를 붙여보세요 · jpakkane/pystd[![README에 뱃지를 붙여보세요](https://git.vaiox.xyz/api/badge/jpakkane/pystd.svg)](https://git.vaiox.xyz/ko/repo/jpakkane/pystd)
<a href="https://git.vaiox.xyz/ko/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 · 총 스타 수(오름차순)

    과소평가 →

최근 30일 추이

누적 스타 추이

순위 추이

같은 보드의 이웃 랭커 · 과소평가

← 랭킹으로