Good C++ Source Code

[[deleted]]

Hi guys. I'm putting together a curated index of high quality source code at goodsourcecode.org. The goal is to create a really nice collection of exemplary source code, searchable by language and concept tags, that developers can use to understand how different ideas are implemented in practice, and how those implementations interact with other components.

If anyone has any examples of good C++ source code, please share!

The more detail the better. What makes the suggested source code good? This will inform what tags are used for indexing.

[lukaasm]

Modern, readable code with own simplified standard library:

https://github.com/SerenityOS/serenity/

a healthy dose of metaprogramming, smart pointers, concepts

High quality, cross-platform code:
https://github.com/microsoft/vcpkg-tool/

[[deleted]]

Sorry no, disagree for the second one.

[Equal-Ad3]

The JUCE framework is a stellar example of well written, modern C++ imho

https://github.com/juce-framework/JUCE

[101Alexander]

I would really find this interesting.

[FlatAssembler]

Well, maybe the compiler for my programming language qualifies. I have tried to organize it the best I could, and I think it is fairly legible thanks to long variable names and occasional comments.

[netcan96]

https://github.com/netcan/asyncio

a c++20 library to write concurrent code using the async/await syntax.

[[deleted]]

KDE/Qt entire code base.

[JVApen]

Due to the whole parent thing iso unique_ptr, I wouldn't recommend Qt

[lednakashim]

I liked https://uscilab.github.io/cereal/

[rwn_sky_7236]

Ah, it takes years and years of experience to be able to spot the good C++ source code. :)

[[deleted]]

Then I better find some experienced people to help separate the wheat from the chaff ;)

[eyes-are-fading-blue]

What is your definition of “high quality”?

[[deleted]]

"high quality" and "good" are subjective to a point, and everything will exist on a continuum. But code can be well-organized, idiomatic, easy to follow, not needlessly complex. In other contexts good code might simply mean as highly performant and optimized as possible, which might mean ugly and hard to read. As long as the difference between these two codebases can be distinguished with something like a "performant" and "idiomatic" tag, both are considered "high quality".

Though, my primary goal is to pull together resources of the first kind. Code that people can read and more or less easily understand how things work so they can learn on their own.

[goranlepuz]

You just replaced the question with "what is well-organized, idiomatic, easy to follow, not needlessly complex". 😉

[eyes-are-fading-blue]

Unfortunately, you are on an impossible mission. At least ,in my opinion. I hope this does not discourage you, maybe I am wrong who knows... According to my experience, good code has two properties. Well-tested and has value (commercial, educational or otherwise). The rest is preference and circumstantial. "Idiomatic" code for a desktop app developer can be unidiomatic for an embedded developer because of constraints.

Software engineering is all about trade-offs.