adios | ADIOS : Architectures Deep In Output Space | Machine Learning library

You have to change and add a few things in order to achieve what you want.

Your UML shows that the Producto class have no temperatura field, Also rename the field refrigerado to nombre as stated in the UML. So remove it and fix the constructor:

The first thing you need when you program any game is that you need a game loop, which runs the game until the user exits it. Interestingly, you opt for recursively calling main, which is also possible (although it could theoretically overload stack, which probably won't happen in this simple case but could be a real problem in a game that loops many times per second for a long time).

So the easiest fix would be to move the playerwins variable out of the main function (then you need to make it static as well) but the correct code that builds better habits for later work would be to use another while loop instead of recursively calling main.

Normally, beginners start with iterative code and discover recursion later, so it is nice that you discover it so early, but unfortunately that is not the correct case for it, but keep it in your pocket for other occasions.

A more modern approach is using flexbox instead of floats. Just add the classes flex and items-center to the parent and let flexbox do it's magic.

The walrus operator is a new addition in Python 3.8. See PEP 572:

https://www.python.org/dev/peps/pep-0572/

One comment :

await only awaits a Promise or an async call (which resolves to a Promise). When you await anything other than a Promise, it returns immediately. Since setTimeout does not return a Promise (it returns a timer ID), the await call on that line returns immediately.

To make that await actually wait for the setTimeout to complete, wrap it in a Promise:

As KamilCuk pointed out, modifying const char* pt1 = "Hello"; gives you an error already at compile time, when you can just fix the code, recompile, and everything is fine. Modifying char* pt1 = "Hello"; throws the error at runtime, and you do not want all your 1 million users to redownload and reinstall your program (You would have to first buy a better internet connection for that). So, you definitely should use const char*.

One possible solution, though I can't help but feel it could be optimised, is as below:

You are almost there—set the alarm first, and call scanf afterwards. The signal will interrupt the call to read() inside scanf(), which causes scanf() to return immediately.