## +24 ## Many Ways to Kill an Orc (or a Hero) ## PATRICE ROY 20 24 September 15 - 20 # Many ways to kill an Orc (or a Hero) Patrice Roy, Patrice.Roy@USherbrooke.ca, Patrice.Roy@clg.qc.ca ## From ng> ## What this is about? // the easy case // ... class Character { /* ... */ }; class Orc; class Hero : Character { int strength_; public: constexpr Hero(std::string_view name, int hit(Orc&); }; A Hero is a Character that can hit an Orc ## What this is about? // the easy case // ... class Character { /* ... */ }; class Orc; class Hero : Character { /* ... */ }; class Orc : Character

Disclaimer and legal notice ..... 472 Acknowledgments ..... 473 Changes for Nim 2.0 ..... 474 ARC/ORC memory management ..... 474 Default values for object fields ..... 475 Overloadable enums .... 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- performance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

Disclaimer and legal notice ..... 468 Acknowledgments ..... 469 Changes for Nim 2.0 ..... 470 ARC/ORC memory management ..... 470 Default values for object fields ..... 471 Overloadable enums .... 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

Disclaimer and legal notice ..... 472 Acknowledgments ..... 473 Changes for Nim 2.0 ..... 474 ARC/ORC memory management ..... 474 Default values for object fields ..... 475 Overloadable enums .... 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- performance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

Disclaimer and legal notice ..... 472 Acknowledgments ..... 473 Changes for Nim 2.0 ..... 474 ARC/ORC memory management ..... 474 Default values for object fields ..... 475 Overloadable enums .... 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- performance of our programs. Additionally, ARC and ORC memory management should bring serious advantages for the creation and performance of threaded and

Disclaimer and legal notice ..... 468 Acknowledgments ..... 469 Changes for Nim 2.0 ..... 470 ARC/ORC memory management ..... 470 Default values for object fields ..... 471 Overloadable enums .... 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

Disclaimer and legal notice ..... 468 Acknowledgments ..... 469 Changes for Nim 2.0 ..... 470 ARC/ORC memory management ..... 470 Default values for object fields ..... 471 Overloadable enums .... 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

Disclaimer and legal notice ..... 468 Acknowledgments ..... 469 Changes for Nim 2.0 ..... 470 ARC/ORC memory management ..... 470 Default values for object fields ..... 471 Overloadable enums .... 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

Disclaimer and legal notice ..... 468 Acknowledgments ..... 469 Changes for Nim 2.0 ..... 470 ARC/ORC memory management ..... 470 Default values for object fields ..... 471 Overloadable enums .... 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

Disclaimer and legal notice ..... 468 Acknowledgments ..... 469 Changes for Nim 2.0 ..... 470 ARC/ORC memory management ..... 470 Default values for object fields ..... 471 Overloadable enums .... 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