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

Update to Approx 0.5 #1380

Merged
merged 2 commits into from Apr 6, 2024
Merged

Update to Approx 0.5 #1380

merged 2 commits into from Apr 6, 2024

Conversation

bluss
Copy link
Member

@bluss bluss commented Apr 6, 2024

Old approx-0_5 feature is removed, the approx feature points to approx 0.5

Uses and supersedes #1063. Closes #1063

@bluss bluss added this to the 0.16.0 milestone Apr 6, 2024
@bluss bluss enabled auto-merge April 6, 2024 13:31
@bluss bluss added this pull request to the merge queue Apr 6, 2024
@@ -193,6 +193,3 @@ macro_rules! impl_approx_traits {

#[cfg(feature = "approx")]
impl_approx_traits!(approx, "**Requires crate feature `\"approx\"`.**");
Copy link
Collaborator

Choose a reason for hiding this comment

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

I guess you want to keep the macro around for the time when approx 0.6 is relevant?

From a code maintenance perspective, getting the code out of the macro would be preferable IMHO.

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm just adapting necessary changes with as low overhead as possible, unfortunately. I'm going for less than perfect for this release 🙂

Keeping the macro doesn't sound so useful no, approx doesn't look like it's going to have a release soon. If you want to fix this, it would be welcome too.

Merged via the queue into master with commit a4764ef Apr 6, 2024
10 checks passed
@bluss bluss deleted the approx-0.5 branch April 6, 2024 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants