We've had backpassing deprecated since August, and if it comes back, it will be in the form of |arg1, arg2| func(123)
instead of arg1, arg2 <- func 123
. We have complexity in the form of detecting commas and arrows that would go away if we were to remove this parsing logic. The desugaring logic is pretty simple, so I don't think it's worth keeping, as it'd be simple to reimplement/copy from git history. Would anyone be opposed to ripping it out for now?
I'm _still_ running into weird edge cases with multi-backpassing in fuzzing, so removing this sounds great to me.
I saw that haha
I'm reviewing your latest PR, I can attempt to remove backpassing once that gets merged (unless you'd rather do it)
:tombstone:
I think it will literally be simpler to reimplement backpassing from scratch than to try to convert the current impl, and that's ignoring the maintenance burden that Joshua keeps carrying like Atlas.
But yes, RIP to backpassing, we hardly knew ye
The other one we should consider removing is the !
desugaring
That can go as soon as Task is gone
We're keeping that operator, but we have purity inference now.
I'd love to remove it! But I don't know when the right time is
Yeah, we probably need to at least promote the basic-cli and basic-webserver releases to latest before we can do that
That's the minimum. basic-ssg
should do a release as well
basic-ssg is already upgraded
Yes, but the latest release is from October
It's just those two... we have them in pre-release to flush out any PI related issues
Oh, it's a prerelease
Oh right... I'm not sure where we got to with the "hyper" upgrade - to remove the ring dependency
Pretty sure that stalled
Ohk, just refreshed. We needed @Anton 's nix magic wand
I'll look at that today
Last updated: Jul 06 2025 at 12:14 UTC