Tecs
EA Standard Template Library
Tecs | EA Standard Template Library | |
---|---|---|
1 | 40 | |
12 | 7,687 | |
- | 0.8% | |
4.4 | 2.1 | |
about 1 month ago | about 1 month ago | |
C++ | C++ | |
MIT License | BSD 3-clause "New" or "Revised" License |
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.
Tecs
-
The joys of writing my own standard library
The engine's ECS is already open source, and that involves a ton of fancy compile-time thread safety checks too. You can check that out here: https://github.com/xthexder/Tecs
EA Standard Template Library
-
Sane C++ Libraries
> you can still use it with smart pointers provided by any other library
Is the point of having a kitchen-sink library like this not that you dont have to reach for a 3rdparty library for things that you need 'all the time'?
Certainly, not everyone needs it.
...but, not everyone needs threads either. Not everyone needs an http server; and yet, if you have an application framework that provides them, when you do need them, it saves you reaching for yet-another-dependency.
Was that no the point from the beginning?
unique_ptr is a fundamental primitive for many, as you see from some other frameworks (1), and implementation is not always either a) trivial, or b) as simple as 'just use std::unique_ptr'.
This does seem like a very opinionated decision with reasonably unclear justification.
[1] - eg. https://github.com/EpicGames/UnrealEngine/blob/release/Engin..., https://github.com/electronicarts/EASTL/blob/master/include/...
- EA Standard Template Library Design
-
The joys of writing my own standard library
Can I introduce you to EASTL
-
Are there any books or tutorials that teach C-Styled C++?
For games focused stuff have a look at EASTL https://github.com/electronicarts/EASTL also perhaps some of the Data Oriented Design stuff (see Mike Acton's CPP Con Talks). This also have loads of good stuff https://www.dataorienteddesign.com/dodbook/
-
I want to start computer graphics programming
C++, but generally treat it as C. STL is pretty slow while debugging so we avoid it and write our own replacements. If you don't want to drive that deep use something like EASTL: https://github.com/electronicarts/EASTL
-
January 2023 Rust Jobs Report
In my experience game devs don't eschew the STL because of compile times, but because (a) its memory management is not sufficiently tunable and (b) it uses exceptions heavily which many game engines disable entirely due to perceived performance problems. For this reason, some of the engines I've worked on have used their own forks of the STL in the spirit of EASTL to rectify these issues. Others like my current project just don't use the STL at all (outside of some third-party library code) and use custom libraries for everything.
-
A container with set interface based on std::vector
In my opinion, you should also benchmark it against something like boost::container::flat_set or eastl::vector_set and you should expect the same performance as with your ordered functionality. Another interesting idea for organization of such flat and sorted container can be found here.
-
Worth it making an own standard library?
finally, if you're worried about performance (a lot of aspiring game programmers seem to be, even though for anything but high-end engines the STL is likely fine if you know what you're doing..) you could look into the EA STL or other STL replacements..
-
What are the hallmarks of well written and high quality C++ code?
check it out: https://github.com/electronicarts/EASTL
-
Where to read about std library implementation?
I just took a look at their atomic.h and wow, "well-documented" is an understatement !