Chris Boesch

> But commits after https://github.com/ratfactor/ziglings/commit/5b47e8ebe6cee0b89dbfe5a2ee413f83d3b7e4e0 have different refs on Codeberg. Actually, no. The refs usually take place via email. And if someone has changed his email, or uses a 'noreply'...

> Sorry, I should've written more clearly. Thanks, now I understand your point. On my local git repository the entries are valid but after I copied it to codeberg they...

Now I know why this no longer works. Commits from different branches were only taken over in the final phase, so the original commits no longer resolve. Codeberg offers the...

> Running specific exercises :+1: Then it should be easy to store the last solved exercise for a faster run. > The disadvantage is that this is not the usual...

I think it should be an improvement. But instead of 'cached' the message should be 'solved'. And then we don't' need the output.

> An issue is that, for some reason, the skipped exercises are not cached. That should not be a problem. > Another issue is that when there are many exercises...

Then leave it like this.

First, we have an issue about that: https://github.com/ratfactor/ziglings/issues/163 Second, the async functions will be back in the next days. Andrew is hard working on it.

Good idea, but where do you actually get stuck? User interaction or reading through a pipe?

Thank you, I will take a look at it. Maybe stage 1 is no longer necessary for compile async. After all, that was an auxiliary construct because of the constant...