Right,core::error is a recent addition, so, it'll need a feature flag. I can add that in with some shenanigans so it always implementsError withstd, but requires the extra feature if it's disabled.

Seems like this would be a breaking change, yes? We haven't really been planning for a 0.2.0 of this crate but I guess it's possible. We can use the opportunity to increase MSRV, too, ideally to a version with the MSRV-aware resolver.

Seems like this would be a breaking change, yes? We haven't really been planning for a 0.2.0 of this crate but I guess it's possible. We can use the opportunity to increase MSRV, too, ideally to a version with the MSRV-aware resolver.

I was mostly being conservative on MSRV since I know people get super picky about it, but yes, this would be a breaking change. I tried to not make ittoo breaking, which is why there are stillis_* aliases, but it is very strictly breaking by changing return types.

If it's a breaking change anyway I think we can update MSRV to the Rust version that contains the MSRV-aware resolver.

I think what we should do then is make a last release in the 0.1.0 stream and have this be the main 0.2.0 change.

Sounds reasonable to me! I'm in no rush to get this merged, so, when you need me to make changes to accommodate whatever decisions get made, I'm down to do that.

For now, things seem to compile with the addition of anerror feature that only implements theError trait when that feature is enabled. With 1.36, that means it won't work if you have the specific combination of--no-default-features --features error, but every other combination works.

I believe thatcore::error was stabilised after the MSRV-dependent resolver, so, we might still want this, but if not, I can remove the feature and just make it always implement the trait.

MSRV-aware resolver is 1.84, from January. The error trait is earlier. So yeah, remove that feature, and add the MSRV.

https://blog.rust-lang.org/2025/01/09/Rust-1.84.0/

I'd like to have this crate have an MSRV that's roughly a year old, and now that the MSRV-aware resolver is a thing bumping the MSRV isn't as annoying to users as it used to be.

Huh, for some reason I thought that feature was much older.

I decided to updaterust-version andedition for this crate too to see what it would affect, and everything seems okay. Feel free to copy those changes to another PR if you'd prefer. I also set the crate version to 0.2.0 since you seemed keen on making this the main 0.2.0 change.

If you wanted to go with 1.85 instead, we could bump up to edition 2024, but since you mentioned only the MSRV-aware resolver, I only bumped to 2021 instead.