Great. But Terminal is not the best place to learn Swift. Playground is way more firndly and powerful. Don't forget to close the thread by marking my correct answer.
You marked your answer as correct, but do not give any answer to your own question. So now, it is unlikely anyone will even try to answer to a solved issue or even read it. But if it's ok for you, that's fine.
You marked your answer as correct, but do not give any answer to your own question. So now, it is unlikely anyone will even try to answer to a solved issue. Good luck.
Memory pressure is relatively high. And you have a large Swap 4 GB). In my example it was 0 GB.
That could well be the cause of the problem. Unfortunately it is not possible to expand memory on M processors…
You marked your "answer" as correct. It is not an anwer, even less a correct answer, just more information. That misleads others who may think they'll find an answer and BTW, much less people will now answer your thread as it is considered solved.
Great. But Terminal is not the best place to learn Swift. Playground is way more firndly and powerful. Don't forget to close the thread by marking my correct answer.
You marked your answer as correct, but do not give any answer to your own question. So now, it is unlikely anyone will even try to answer to a solved issue or even read it. But if it's ok for you, that's fine.
You marked your answer as correct, but do not give any answer to your own question. So now, it is unlikely anyone will even try to answer to a solved issue. Good luck.
Memory pressure is relatively high. And you have a large Swap 4 GB). In my example it was 0 GB.
That could well be the cause of the problem. Unfortunately it is not possible to expand memory on M processors…
You marked your "answer" as correct. It is not an anwer, even less a correct answer, just more information. That misleads others who may think they'll find an answer and BTW, much less people will now answer your thread as it is considered solved.