You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a human-readable error message retrieval method to the Diagnostics
struct, making it easier to log and understand failures from curl
operations. Refactor Multi to always include diagnostics and to return
detailed error information for each operation. Update examples and
documentation to illustrate the new diagnostics workflow.
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.org
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
#+TITLE: zig-curl
2
2
#+DATE: 2023-09-16T23:16:15+0800
3
-
#+LASTMOD: 2025-10-17T09:10:36+0800
3
+
#+LASTMOD: 2026-03-08T11:50:51+0800
4
4
#+OPTIONS: toc:nil num:nil
5
5
#+STARTUP: content
6
6
@@ -61,6 +61,23 @@ pub fn main() !void {
61
61
62
62
Check [[file:examples]] for more examples.
63
63
64
+
** Diagnostics
65
+
When a curl operation fails, it returns a generic =error.Curl=. To get more detailed information, you can use the =diagnostics= field in =Easy= or =Multi=.
0 commit comments