templight
circle
templight | circle | |
---|---|---|
4 | 55 | |
704 | 2,228 | |
- | - | |
4.0 | 5.0 | |
about 2 months ago | 7 months ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
templight
-
static_assert is all you need (no leaks, no UB)
IMHO the best approach is to avoid the problem by applying TDD. Then there is very little need to debug anything. But otherwise, there is https://github.com/mikael-s-persson/templight for compile-time debugging which is pretty cool and having something like `expect(auto... args) static_asert(args...); assert(args...);` may help with being able to debug at run-time and get the coverage (though, the code has has to compile aka pass first).
-
[C++20][safety] static_assert is all you need (no leaks, no UB)
For sure. There has been https://github.com/mikael-s-persson/templight and https://github.com/metashell/metashell. The former allowed to basically step into the compilation process (after the fact).
-
[C++26*] Rise of the static reflection(s)
Double not sure whether practical, though, https://github.com/mikael-s-persson/templight approched the problem back in the day
-
Query a compilation database (lsp, ccls, rtags, ...)
Is there a function in lsp-mode, or ccls directly to find the compilation command associated with the file (if any) in the current buffer? If not, would another package (rtags, ede-compdb, irony-cdb) help query the compilation database without needing to use the rest of the package? The main use case is to plug it into other tools such as rmsbolt and templight that "compile" code to provide additional information.
circle
- Rusty.hpp: A Borrow Checker and Memory Ownership System for C++20
-
How difficult would it be to make a c++ compiler
Sean Baxter created a front end c++ compiler by himself, using llvm for the back end and the gcc or clang stl. I think it took him a couple of years. https://www.circle-lang.org/. Before this happened I heard a couple of different people claiming that there would never be a totally new compiler as it was too much work.
-
Toward a TypeScript for C++"
The real Typescript for C++ is Circle.
https://www.circle-lang.org/
Just like Typescript to JavaScript, the syntax is an evolution of what already exists, not a completely different syntax.
-
A Metaobject Protocol for C++ [pdf]
Sean Baxter's Circle [1] is arguably the spiritual successor to MOP.
[1] https://www.circle-lang.org/
-
Circle Evolves C++ [video]
Context: https://github.com/seanbaxter/circle/blob/master/new-circle/...
Note that Circle is not an F/OSS compiler as someone pointed out before. This however doesn't make Circle less relevant, because it is actually a testament to show that C++ could have been much better without the claimed breakage. If Circle does provide a number of desirable features and its compiler can be built by a single person, then why shouldn't the committee do the same?
-
My (Herb Sutter's) C++ Now 2023 talk is online: “A TypeScript for C++”
From all wannabe C++ replacements candidates, the only language that is really a TypeScript for C++, is Circle.
For whatever reason, Herb Sutter decided to ignore this language on the presentation.
https://www.circle-lang.org/
This is the only one with the syntax based on C++, incrementally changing the features via #pragma settings.
"Circle Fixes Defects, Makes C++ Language Safer & More Productive"
https://www.youtube.com/watch?v=x7fxeNqSK2k
"Circle Evolves C++"
https://www.youtube.com/watch?v=P1ZDOGDMNLM
- File for Divorce from LLVM
-
Making C++ Safe Without Borrow Checking, Reference Counting, or Tracing GC
The second someone makes a successor language that seamlessly/directly interops with C++ _AND_ has the level of build/IDE tooling that C++/Rust have, I'm on board.
The closest thing right now is Sean Baxter's "Circle" compiler in "Carbon" mode IMO:
https://github.com/seanbaxter/circle/blob/master/new-circle/...
Unfortunately, Circle is closed-source and there's no LSP or other tooling to make the authoring experience nice.
- Circle-lang: A feasible, simple, and immediate way for C++ to break out of the rut it's been in. Surprised more people aren't talking about it.
-
Recurrence-expression is a programmable superset of fold-expression
I read through the whole of https://github.com/seanbaxter/circle/blob/master/new-circle/README.md and man, I'm drooling. Awesome work, kudos.
What are some alternatives?
rmsbolt - pony mode WIP
raspberry-pi-os - Learning operating system development using Linux kernel and Raspberry Pi
TDD - See while you code
dts2hx - Converts TypeScript definition files (d.ts) to haxe externs (.hx) via the TypeScript compiler API
metashell - C++ metaprogramming shell
mdspan - Reference implementation of mdspan targeting C++23
examc - proof of concept C unit test library using linker sections
papers - ISO/IEC JTC1 SC22 WG21 paper scheduling and management
rtags - A c/c++ client/server indexer with for integration with emacs based on clang.
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
ut - C++20 μ(micro)/Unit Testing Framework
meta