Skip to content

Support auto_impl on borrowed references #4

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

Merged
merged 1 commit into from
Oct 7, 2017
Merged

Conversation

KodrAus
Copy link
Member

@KodrAus KodrAus commented Oct 7, 2017

Closes #3

I've added a poor-man's parser for the #[auto_impl] attribute so we can parse & and &mut correctly. We could probably do a better job of sharing code for smart pointers and reference types and dealing with malformed input, but this should be good enough.

@KodrAus KodrAus merged commit 53a2e89 into master Oct 7, 2017
@@ -1,6 +1,6 @@
[package]
name = "auto_impl"
version = "0.1.1"
version = "0.1.2"
Copy link

@bjorn3 bjorn3 Oct 7, 2017

Choose a reason for hiding this comment

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

This should be 0.2.0 as this pr is a functional change.

http://semver.org/#spec-item-6

  1. Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
  2. Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

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 think it's pretty common in the Rust ecosystem to use the patch version effectively as the minor is post 1.0 when the crate is pre 1.0, since we're only utilising two versions and aren't technically bound by semver anyways in 0.x.

If there's code that was accepted in 0.1.1 that isn't in 0.1.2 then I've messed up.

Copy link

Choose a reason for hiding this comment

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

I see.

@KodrAus KodrAus deleted the feat/auto-ref branch October 7, 2017 13:18
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.

2 participants