Is it expected that I can call an unstable method on
MaybeUninit inside libcore without declaring the feature gate? But somehow this does not seem to happen consistently...
seems like I cannot use unstable macros, but I can use unsable library methods
that's a bummer, I thought I was using fine-grained feature gates to limit what part of the API libcore itself can use
there is a feature for that
#[allow_internal_unstable] I think its called, it used to enable using all features, but last week that changes and you have to specify which features you want to use
so you might want to check if there is one of those "somewhere" enabling the feature gating those particular methods
I'd be surprised if libcore used these for, like, its entire content