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

Switch to go-multierror in 4 remaining locations #3336

Merged
merged 1 commit into from
Oct 4, 2015
Merged

Switch to go-multierror in 4 remaining locations #3336

merged 1 commit into from
Oct 4, 2015

Conversation

svanharmelen
Copy link
Contributor

It seems there are 4 locations left that use the helper/multierror package, where the rest is TF settled on the hashicorp/go-multierror package.

Functionally this doesn’t change anything, so I suggest to delete the builtin version as it can only cause confusion (types from both packages are called multierror.Error but they are still different Go types).

It seems there are 4 locations left that use the `helper/multierror`
package, where the rest is TF settled on the `hashicorp/go-multierror`
package.

Functionally this doesn’t change anything, so I suggest to delete the
builtin version as it can only cause confusion (both packages have the
same name, but are still different types according to Go’s type system.
@stack72
Copy link
Contributor

stack72 commented Sep 28, 2015

👍 nice to see a PR removing code :)

@apparentlymart
Copy link
Contributor

👍 Seems like a great idea to reduce confusion.

@apparentlymart apparentlymart merged commit 2ba8dc3 into hashicorp:master Oct 4, 2015
apparentlymart added a commit that referenced this pull request Oct 4, 2015
Instead, use ``github.com/hashicorp/go-multierror``.
@svanharmelen svanharmelen deleted the f-core-multierror branch October 5, 2015 11:07
@ghost
Copy link

ghost commented Apr 30, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants