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.

Sign up for GitHub

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

Jump to bottom

Remove Errors channel #2

Open
nathany opened this issue Jun 28, 2014 · 1 comment
Open

Remove Errors channel #2

nathany opened this issue Jun 28, 2014 · 1 comment
Labels
v2 Changes that are not compatible, but can possibly be done in v2

Comments

@nathany
Copy link
Contributor

nathany commented Jun 28, 2014

As per the API document, we would like to replace the Errors channel with an Err() method and close the channel on fatal errors.

The question is how to handle non-fatal errors (if any).
@nathany nathany added the api label Jun 28, 2014
@nathany nathany mentioned this issue Jun 28, 2014
Closed
@nathany nathany mentioned this issue Jul 21, 2014
Closed
@nathany nathany added this to the Version 2 API milestone Aug 17, 2014
@nathany nathany mentioned this issue Dec 16, 2015
Closed
@matthias-stone
Copy link
Contributor

An example of a non-fatal error is ErrEventOverflow.

djoyner pushed a commit to SpirentOrion/fsnotify that referenced this issue Jan 6, 2021
Merge pull request fsnotify#2 from windmilleng/jazzdan/fix_debug_macos
0b53a2c 
Fix debugging on macos
This was referenced Feb 28, 2022
Closed
Merged
@arp242 arp242 removed this from the v2 Internals milestone Jul 29, 2022
@arp242 arp242 added v2 Changes that are not compatible, but can possibly be done in v2 and removed API labels Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
v2 Changes that are not compatible, but can possibly be done in v2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nathany @arp242 @matthias-stone