I mean there wouldn't be any rewritten history, the merged PRs would just be a fast-forward merge, i.e. there wouldn't be a merge commit so whoever is working on top of your branch can just...
I have several ziglings work trees checked out on which I work and test in parallel. For this reason, I am not a fan of rebasing merely to make the history look prettier. It only creates chaos....
because of the fixup?
The reason I wanted to hear your opinion first (before it being merged) was so that we could rebase --autosquash before merging to have a cleaner history.
std.lang.Type definitions is changed, affecting exercises: 65, 71, 82.
Checked the image again, but it still doesn't run the latest version, it's running a version from 5th of April ([284ab0ad8](284ab0ad86...
I'd rather put it in 028_defer2 then since 027_defer introduces the concept and 028_defer2 tries to teach something more interesting.
Exercise 27 introduces the concept of the defer keyword, and only one defer statement is needed to solve the exercise.
std.lang.Type definitions is changed, affecting exercises: 65, 71, 82.
It should definitely be there, as OP pointed out:
std.lang.Type definitions is changed, affecting exercises: 65, 71, 82.
Any thoughts about this as a way forward?