Starting in on the #bevy release notes for 0.14 today! So, so many small PRs: for both the tools and the individual content sections.
I have a half-dozen open right now; give me a review or two (low standard, these will get a real editing pass before publication) and help me start tomorrow's work with a fresh slate? 🥺
@alice_i_cecile do you need someone with contributor/reviewer status to do the review?
They all look good to me, except 1198 has some TODOs in it (intentional?), and the rounded corners note is a bit non specific about what can be rounded, it’d be great to add a sentence for that.
in git, what ways are there to "lose" a commit in a way that you CAN'T recover using the reflog (so that you need to iterate over every single commit in the repository if you want to find it?
The only ways I know (using git's normal tools) are:
using git stash drop or git stash pop to drop a stashed commit
waiting 90+ days to try to recover the commit (so that it expires from the reflog)
explicitly deleting the reflog in some way (rm -rf .git, git reflog expire, etc)
@b0rk if it was detached, or you have certain branch configs, then I think git gc can do it. I think similar commands can be configured to run automatically when your repo is large or slow.
@b0rk I think I’ve had detached commits lost due to the automatic cleanup because it was a large repo. Although it was a long time ago, and I don’t remember the exact diagnosis sorry.
@b0rk Yeah, I’m fairly sure it was git prune as part of automatic gc due to a large slow repo. This thing: “Auto packing the repository for optimum performance […]".
@b0rk It was a commit I cared about, which I detached through an explicit mistake (like reset), but I pruned it due to a much more unexpected implicit mistake. I believe it was pruned when fetching to see if the lost commit had been pushed.
@eniko apparently Bluey has surpassed Dundee’s popularity and was the second most streamed show of 2023. I’m not at all sad to be represented by Bluey over Dundee tbh.
My take: Swift Concurrency has gone from being somewhat understandable to being really, really hard to apply and understand properly.
I get that we can stick with Swift 5 language mode, but none of us wants to do that.
I hope that WWDC brings some understandable instruction alongside improved tooling, because right now we're all reliant on @mattiem sharing what he has worked out (thanks Matt!).
@holly I’m not using Swift at the moment, but very interested in what it’s doing! I’d love a clear and concise definition of isolated and non-isolated. I haven’t found one on any of the official docs I’ve seen. This might just be googleability. However, I imagine errors using those terms will only be as clear as the terms themselves.
I’m guessing from context; the English definition; and a proposal that mentioned “data isolation”, that isolated means it doesn’t pass between concurrency contexts, non-isolated means it does/can. I’m guessing implementing Sendable is one way to make something safely non-isolated.
Although all the official blogs and proposals I’ve seen seem to assume you already know what they mean and what their relationship to each other is (in the context of Swift concurrency). Non-official blogs I’ve seen seem to try and exhaustively define whether something is isolated, as that’s a thing that crops up in errors, but it seems to me like a good definition would save the need for that exhaustivity.
@eniko Ivory on iOS has it as “hide this post” and I think Tusky is the Android app that’s most often compared to Ivory, so maybe that one is what you want
@eniko this isn’t computer science academics, more like biology or something like that. Although the pseudocode or math in a paper normally has actual code somewhere that validated it, unless they share a proof, and I believe that code is what they do.
@eniko yeah sorry, the only one I know without that last five words is https://rosettacode.org/ for common algorithms (or optimistically searching for the paper title on github/gitlab)