Rick van Dam

Some instructions here: https://blog.ostermiller.org/git-remove-from-history The fact that all users of this repo will have to do something makes this non trivial. You are basically rewriting the history but that history...

I have been using git flow professionally lately too and so far I like it. Sourcetree even has built in support for it.

2 years later and I would suggest its better to look at something like githubflow. Having a separate develop and master doesn't give you any advantages but can cause some...

Well usually when you use .net core you have a executable but its not a requirement :P

So the only thing thats blocking is the GLControl @SirePi? If we can get around that we could use the new opentk and change everything to netcore?

Maybe BB code would work

> A possible solution, as proposed by @Barsonax, would be to assign to each GameObject (and/or Component) a list of Coroutines that would be automatically Cancelled once their respective "container"...

Another thing we might want to look into in the future: https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.iasyncenumerable-1?view=dotnet-plat-ext-3.1 Basically the combination of a itterator and async

> So, I was thinking.. would it be interesting to add in v4 a WaitUntil.CoroutineEnds(IEnumerable coroutine) that would yield until the sub-coroutine ends? (IsAlive is true) Thats a neat idea....

> Would a restructuring of WaitUntil like this be bad? (comments removed) I think so. Not because the code is bad but because relying on delegates with a closure for...