Jason Turner
Jason Turner
Currently two sample goals exist, this issue should be used to track a specific set of lessons that we might want to implement.
Current UI is cumbersome, we need some way to have it better organized / dockable. The current experimental dockable branch on imgui should help https://github.com/ocornut/imgui/tree/docking
We'll prefer ChaiScript (for obvious reasons) for the scripting technology. The current interface to the lessons / goals can be found here: https://github.com/lefticus/cpp_box/blob/2da3c85acbc64356af9a7a29a52e702c9f0c0308/src/cpp_box.cpp#L580-L608
They should result in a call to the unhandled opcode vector Which should by default log / emit / somehow log that what the unhandled opcode was so it can...
You can see here in codecov that the unit tests are only covering about 1/2 of the possible Data Processing instructions that the ARM supports. https://codecov.io/gh/lefticus/cpp_box/src/master/include/cpp_box/arm.hpp#L725...742 You can see details...
I've started the hardware design on the wiki https://github.com/lefticus/arm_thing/wiki/Memory-Map Soliciting comments if you have any, @mattgodbolt and @jonathandturner
* cover normal algorithm adapters (ie find_if) * cover basics of using `|` for composing of range views * show string split utility * show constexpr
`std::any`, `std::function` and `std::string` each have optimizations that avoid heap allocations for the case of "small" objects. How do these optimizations work?
Books to reference: * [Head First Design Patterns](https://amzn.to/3CQHKmS) (Java) * [Design Patterns](https://amzn.to/3QeoJhd) (Classic Gang-of-Four / Pre-ISO C++) * [Hands on Design Patterns with C++](https://amzn.to/3emBqcD) * [Design Patterns in Modern C++20](https://amzn.to/3RgBJ7n)...