Many ways to kill an Orc (or a Hero) Patrice Roy, Patrice.Roy@USherbrooke.ca, Patrice.Roy@clg.qc.caFrom the abstract… • « Our game programmers and game engines involve fights between heroes and their other things)What this is about? // the easy case // ... class Character { /* ... */ }; class Orc; class Hero : Character { int strength_; public: constexpr Hero(std::string_view name, int Character::suffer; void hit(Orc&); }; 17 A Hero is a Character that can hit an OrcWhat this is about? // the easy case // ... class Character { /* ... */ }; class Orc; class Hero : Character {

The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory avoids GC-generated delays, and may increase the performance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and supports ORC/ARC memory handling, a form of scope- and destructor-based automatic memory management. ARC can be used when our memory blocks have no cycles, which is often the case. And ORC can handle

The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory avoids GC-generated delays, and may increase the performance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and supports ORC/ARC memory handling, a form of scope- and destructor-based automatic memory management. ARC can be used when our memory blocks have no cycles, which is often the case. And ORC can handle

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 ARC/ORC memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory GC-generated delays, and may increase the per­ 4 formance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 ARC/ORC memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory avoids GC-generated delays, and may increase the perfor­ mance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 ARC/ORC memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory GC-generated delays, and may increase the per­ 4 formance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 ARC/ORC memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory avoids GC-generated delays, and may increase the perfor­ mance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 ARC/ORC memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory avoids GC-generated delays, and may increase the perfor­ mance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 ARC/ORC memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory avoids GC-generated delays, and may increase the perfor­ mance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 ARC/ORC memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The most significant change in Nim 2.0 is that ORC memory management has become the default indicating that it is considered ready for use in production. ORC gives us GC-like, fully deterministic memory avoids GC-generated delays, and may increase the perfor­ mance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and