Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(quaint): remove chrono conditional flag #4227

Merged
merged 2 commits into from
Sep 13, 2023
Merged

Conversation

jkomyno
Copy link
Contributor

@jkomyno jkomyno commented Sep 12, 2023

@jkomyno jkomyno changed the title feat(quaint): remove "chrono" conditional flag feat(quaint): remove chrono conditional flag Sep 12, 2023
@codspeed-hq
Copy link

codspeed-hq bot commented Sep 12, 2023

CodSpeed Performance Report

Merging #4227 will not alter performance

Comparing feat/quaint-remove-chrono (bd89353) with main (9e8c303)

Summary

✅ 11 untouched benchmarks

@jkomyno jkomyno marked this pull request as ready for review September 13, 2023 04:54
@jkomyno jkomyno requested a review from a team as a code owner September 13, 2023 04:54
Comment on lines -340 to -349
#[cfg(not(feature = "chrono"))]
typ => {
let msg = format!(
"Value of type {:?} is not supported with the current configuration",
typ
);

let kind = ErrorKind::conversion(msg);
Err(Error::builder(kind).build())?
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is worth double-checking.
However, since this PR effectively acts as if the chrono feature was applied 100% of the time, it should be safe to remove.

@jkomyno jkomyno added this to the 5.4.0 milestone Sep 13, 2023
@miguelff miguelff merged commit 5106138 into main Sep 13, 2023
62 of 64 checks passed
@miguelff miguelff deleted the feat/quaint-remove-chrono branch September 13, 2023 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants