https://github.com/go-warnings/warnings

Last synced: about 2 months ago

Repository metadata:

Package warnings implements error handling with non-fatal errors (warnings).

Owner metadata:

Committers metadata

Last synced: about 2 months ago

Total Commits: 6
Total Committers: 1
Avg Commits per committer: 6.0
Development Distribution Score (DDS): 0.0

Commits in past year: 0
Committers in past year: 0
Avg Commits per committer in past year: 0.0
Development Distribution Score (DDS) in past year: 0.0

Name Email Commits
speter s****1@g****m 6

Issue and Pull Request metadata

Last synced: about 2 months ago

Package metadata

go: gopkg.in/warnings.v0

Package warnings implements error handling with non-fatal errors (warnings). A recurring pattern in Go programming is the following: This pattern allows interrupting the flow on any received error. But what if there are errors that should be noted but still not fatal, for which the flow should not be interrupted? Implementing such logic at each if statement would make the code complex and the flow much harder to follow. Package warnings provides the Collector type and a clean and simple pattern for achieving such logic. The Collector takes care of deciding when to break the flow and when to continue, collecting any non-fatal errors (warnings) along the way. The only requirement is that fatal and non-fatal errors can be distinguished programmatically; that is a function such as must be implemented. The following is an example of what the above snippet could look like using the warnings package: For an example of a non-trivial code base using this library, see gopkg.in/gcfg.v1 Rules for using warnings TODO

  • Homepage: https://github.com/go-warnings/warnings
  • Documentation: https://pkg.go.dev/gopkg.in/warnings.v0#section-documentation
  • Licenses: BSD-2-Clause
  • Latest release: v0.1.2 (published about 7 years ago)
  • Last Synced: 2024-11-22T01:39:27.176Z (about 1 month ago)
  • Versions: 3
  • Dependent Packages: 6,987
  • Dependent Repositories: 40,961
  • Docker Downloads: 16,470,681,038
  • Rankings:
    • Docker downloads count: 0.026%
    • Dependent repos count: 0.027%
    • Dependent packages count: 0.027%
    • Average: 5.996%
    • Forks count: 13.461%
    • Stargazers count: 16.437%
go: github.com/go-warnings/warnings

Package warnings implements error handling with non-fatal errors (warnings). A recurring pattern in Go programming is the following: This pattern allows interrupting the flow on any received error. But what if there are errors that should be noted but still not fatal, for which the flow should not be interrupted? Implementing such logic at each if statement would make the code complex and the flow much harder to follow. Package warnings provides the Collector type and a clean and simple pattern for achieving such logic. The Collector takes care of deciding when to break the flow and when to continue, collecting any non-fatal errors (warnings) along the way. The only requirement is that fatal and non-fatal errors can be distinguished programmatically; that is a function such as must be implemented. The following is an example of what the above snippet could look like using the warnings package: For an example of a non-trivial code base using this library, see gopkg.in/gcfg.v1 Rules for using warnings TODO

  • Homepage: https://github.com/go-warnings/warnings
  • Documentation: https://pkg.go.dev/github.com/go-warnings/warnings#section-documentation
  • Licenses: BSD-2-Clause
  • Latest release: v0.1.2 (published about 7 years ago)
  • Last Synced: 2024-11-11T01:13:24.336Z (about 2 months ago)
  • Versions: 3
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Rankings:
    • Dependent packages count: 6.999%
    • Forks count: 7.013%
    • Average: 7.829%
    • Stargazers count: 7.96%
    • Dependent repos count: 9.346%