Cfrtjryk

0 In my literature review introduction, I open up my second paragraph explaining some background information on my topic. I bring up the gap in research in the 2nd paragraph. Here is both the first, second, and third paragraph: "In response to the current geopolitical crises plaguing the Middle East, specifically the Syrian Civil, the war in Afghanistan, and instability in Iraq, the countries of Western Europe have experienced a substantial influx of refugees. During 2015, over a million migrants crossed into Europe seeking asylum, a number unprecedented in in recent history (“Asylum Statistics” 2018). Alongside the societal, political, and humanitarian aspects, the economic impact of Europe’s migration crisis has become a growing concern. Whether refugees contribute to or deplete public budgets of develop

1 I decided to give Go a try and implemented a Game of Life Kata exercise in GOLang. I have no prior experience in Go and the majority of my experience comes from Java, C#, and Python. My code appears to be working as intended but not sure if I've implemented it in the GO way, or idiomatic Go. I've seen a few Go examples online where the properties of the struct were always public, but that feels foreign coming from the object-orient world. The way I've implemented it the Board struct should never be able to get into an invalid state. I don't know if that is a mindset that is shared by the Go community. I have a colleague who is big into Go and favors immutability and no side effects. I can see how that would be ideal for concurrency, but does the general Go community prefer avoiding mutations? As an