Closed ChrisDenton closed 3 months ago
no idea.
after 1.77.1 gets out the door tomorrowish this can become fixing up our CI in general and removing the hack.
1.77.1 is released but now something else is broken in nightly.
Oh rustc-serialize, gah. Why do we still have that, lol.
Ok, everything is working again except for the binary size check problem.
now that deriving RustcDecodable
and RustcEncodable
is officially officially unstable, how would you feel about removing it? I feel like maybe we should bite that bullet before being forced to?
Hell yeah let's fucking kill that shit off.
backtrace 0.4 here we come.
Yay! 🥳 Should that be a separate PR?
I honestly do not care.
Your enthusiasm is infectious so I've just done it right here right now.
Nice.
backtrace 0.4 here we come.
Technically you don't even need to. If cargo fails to find a feature in one crate version it will look for other crate versions for one which does have the feature. So if anyone depends on the rustc-serialize feature, cargo will simply force usage of an older backtrace version which still supports rustc-serialize.
Oh cool.
If it was a feature I expected people to realistically depend on I'd worry about this but nah.
@workingjubilee I'm not clear why we weren't doing this already. It would have caught the stripping issue earlier. There's a very old comment about only testing on nightly but that's the opposite of what we were doing.
Obviously this will still currently fail CI until rustc or cargo is patched.