List view
Stuff after the library is "feature-complete".
No due dateSince a goal of this library is to be as fast to comprehend as possible (low-turnaround for extending), it will have a very thorough set of documentation. I would like to convey a vibe similar to the old manuals and documentation that seems to be lost to stack overflow and now GPT abuse.
No due date•3/3 issues closedThings unrelated directly to the frontend interface, or the frontend user does not directly handle. It should be a more "finalized" state where we wont be changing the default allocators anymore, the Data-type won't change, and instead from that point forward only performance passes may be completed.
No due date•4/11 issues closedIt will not be standard compliant, but this should mean that the user should get an AST that can validate all content of a C++ file, excluding preprocessor edge cases that are unsupported.
No due date•2/10 issues closed- No due date•0/5 issues closed
Core frontend features for the library that the user will directly experience a result from. These are unrelated to the auxiliary tools or interfaces provided, just the AST construction & serialization interface.
No due date•6/16 issues closedThe current "testing" for the library are the following: * genc lib * Project bootstrap * Singleheader gen * Sanity test that stress tests on large resource consumption. * SOA mock generation * Scanning unreal files (not in this repo) Nice to have in this repo - Order of priority: * Fail cases * Every conditional option for the upfront constructors * Every conditional option covered for serialization. * Every conditional option covered for parse constructors The most expensive to test is the operator validation. * Could make a wrapper for a s128 and define all the operator overloads for it. Can have two variants, one with the overloads as a member functions, the other as a bare pod struct with overloads.
No due date•2/10 issues closed