Add go-deepcopy

[tiendc]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/tiendc/go-deepcopy
• pkg.go.dev: https://pkg.go.dev/github.com/tiendc/go-deepcopy
• goreportcard.com: https://goreportcard.com/report/github.com/tiendc/go-deepcopy
• coverage service link (codecov, coveralls, etc.): https://codecov.io/gh/tiendc/go-deepcopy

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

[github-actions]

Thank you for contributing to awesome-go. We will review your contribution as soon as possible.

Make sure you add the links in the body of the pull request that are requested in the contribution guide:

• repo link
• pkg.go.dev
• goreportcard.com
• coverage

Your project is under review. It may take a few days to be approved.

[yassinebenaid]

• The exported types are not documented (mostly).

CONTRIBUTING.md

be thoroughly documented (README, pkg.go.dev doc comments, etc.) in the English language, so everyone is able to understand the project's intention and how it works. All public functions and types should have a Go-style documentation header;

[tiendc]

@yassinebenaid
I added some docs. Could you review it again?
Thanks

[phanirithvij]

This is not in a right category

[tiendc]

This is not in a right category

I see another Copier one is in the group, DeepCopier. Could you point out which is the one more suitable?

[yassinebenaid]

Should we add a new category called Reflection (or similar) under which all reflect based projects will be listed ? @phanirithvij

Examples:

• Deepcopier - Simple struct copying for Go.
• copy - Package for fast copying structs of different types.
• gpath - Library to simplify access struct fields with Go's expression in reflection.
• objwalker - Walk by go objects with reflection.
• reflectutils - Helpers for working with reflection: struct tag parsing; recursive walking; fill value from string.

And

• go-deepcopy - Fast deep copy library.