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

start using GError #563

Open
michalfabik opened this issue May 27, 2019 · 2 comments
Open

start using GError #563

michalfabik opened this issue May 27, 2019 · 2 comments
Assignees

Comments

@michalfabik
Copy link
Contributor

As suggested by @ernestask.

@ernestask
Copy link
Collaborator

ernestask commented May 27, 2019

Needs more context.

It’s for things like

If one decided to also output the format file name when an error occurs, one would also need to start adding random parameters to the function. However, if we just took, say, a GError ** in each failable function, we format the output however we want from callers, since they usually have what is missing; one can propagate errors up the call stack to no end (well, not really).

@ernestask ernestask self-assigned this Jun 5, 2019
@ernestask
Copy link
Collaborator

Created a branch locally, but haven’t had time to actually work on it.

@xsuchy xsuchy added this to Needs triage in Issue review via automation Apr 9, 2020
@xsuchy xsuchy moved this from Needs triage to Yes in Issue review Apr 9, 2020
@xsuchy xsuchy moved this from Yes to Maybe in Issue review Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Issue review
  
Maybe
Development

No branches or pull requests

2 participants