2019-03-02 16:46:04 -05:00
|
|
|
|
2021-10-04 23:47:27 -07:00
|
|
|
|
2017-12-23 22:08:53 -05:00
|
|
|
|
2017-05-28 15:54:53 +02:00
|
|
|
|
2017-12-23 22:08:53 -05:00
|
|
|
|
2018-09-13 16:34:33 -04:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
2019-02-08 18:18:47 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-10-04 23:47:27 -07:00
|
|
|
|
2016-05-17 13:32:43 -07:00
|
|
|
|
2020-11-12 03:13:19 +01:00
|
|
|
|
|
|
|
|
|
2021-10-04 23:47:27 -07:00
|
|
|
|
2019-05-24 18:27:18 -04:00
|
|
|
|
2021-10-04 23:47:27 -07:00
|
|
|
|
2020-10-28 17:39:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-13 22:59:06 +07:00
|
|
|
|
2019-05-24 18:27:18 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-02-04 23:04:49 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-07 22:35:15 -07:00
|
|
|
|
2016-05-08 01:34:00 -07:00
|
|
|
|
2020-06-26 19:29:06 -06:00
|
|
|
|
|
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2021-10-29 03:00:00 +01:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2021-10-29 03:00:00 +01:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
|
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2021-10-29 02:08:41 +01:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-29 02:08:41 +01:00
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
|
|
|
|
|
2020-08-08 00:34:13 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2020-08-08 00:34:13 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2020-08-08 00:34:13 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-08-07 22:35:15 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
|
|
|
|
|
2023-06-15 13:14:16 +06:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
|
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2020-08-07 22:35:15 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2020-08-07 22:35:15 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2020-08-07 22:35:15 -07:00
|
|
|
|
2020-08-08 00:34:13 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2020-08-07 22:35:15 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2021-11-06 00:54:35 +00:00
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2021-11-06 00:54:35 +00:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2021-11-06 00:54:35 +00:00
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-11-06 00:54:35 +00:00
|
|
|
|
2023-06-08 13:30:28 +10:00
|
|
|
|
|
|
|
|
|
2021-11-06 00:54:35 +00:00
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2020-06-26 19:29:06 -06:00
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-30 18:02:08 +01:00
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
|
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
|
|
|
|
|
2021-10-29 04:17:21 +01:00
|
|
|
|
2021-10-29 00:41:58 +01:00
|
|
|
|
2021-10-29 04:17:21 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
|
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2021-06-19 21:10:22 -04:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2021-06-19 21:10:22 -04:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2020-05-06 23:56:48 -06:00
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-10-29 04:17:21 +01:00
|
|
|
|
|
|
|
|
|
2020-05-06 23:56:48 -06:00
|
|
|
|
|
|
|
|
|
2021-09-22 05:09:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
|
|
|
|
|
2021-09-22 05:09:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
|
|
|
|
|
2021-09-22 05:09:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-27 17:26:16 -07:00
|
|
|
|
|
|
|
|
|
2023-04-26 13:57:08 -07:00
|
|
|
|
|
|
|
|
|
2016-05-17 13:32:43 -07:00
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:19 +01:00
|
|
|
|
2023-04-26 13:57:08 -07:00
|
|
|
|
|
|
|
|
|
2016-12-12 00:31:35 -05:00
|
|
|
|
|
|
|
|
|
2018-07-13 23:01:21 +02:00
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:19 +01:00
|
|
|
|
2018-07-13 23:01:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-23 14:28:14 -04:00
|
|
|
|
2018-07-13 23:01:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-27 17:26:16 -07:00
|
|
|
|
2016-08-11 22:25:13 -07:00
|
|
|
|
2020-02-24 22:15:04 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-06 21:38:11 +01:00
|
|
|
|
2023-04-23 20:06:21 +02:00
|
|
|
|
2020-01-06 21:38:11 +01:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-24 22:15:04 +01:00
|
|
|
|
2022-08-05 14:47:52 +02:00
|
|
|
|
2022-06-12 00:56:01 -07:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
2023-04-27 17:26:16 -07:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-24 22:15:04 +01:00
|
|
|
|
2021-12-28 08:03:11 +03:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-24 22:15:04 +01:00
|
|
|
|
|
|
|
|
|
2022-11-09 16:33:48 +01:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-11-09 16:33:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-24 22:15:04 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-06 13:43:50 -04:00
|
|
|
|
|
|
|
|
|
2020-02-24 22:15:04 +01:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-05-08 19:02:15 +03:00
|
|
|
|
2020-04-01 09:11:05 +01:00
|
|
|
|
2020-03-30 02:57:50 +01:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
2020-05-24 22:31:51 +05:00
|
|
|
|
2023-07-06 19:48:42 +02:00
|
|
|
|
2020-05-24 22:31:51 +05:00
|
|
|
|
2020-08-20 10:08:27 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-13 22:30:06 +01:00
|
|
|
|
2020-08-20 10:08:27 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
2020-01-06 21:38:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2022-12-06 20:35:50 -07:00
|
|
|
|
2022-07-03 15:39:39 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-06 21:38:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
2021-12-28 08:03:11 +03:30
|
|
|
|
|
|
|
|
|
2020-04-18 19:44:59 +03:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-18 19:44:59 +03:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
2020-04-18 19:44:59 +03:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
2020-02-24 22:15:04 +01:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
2022-11-09 16:33:48 +01:00
|
|
|
|
2020-04-18 19:44:59 +03:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
2022-07-03 15:39:39 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
2020-05-08 19:02:15 +03:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-28 08:03:11 +03:30
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-09 16:33:48 +01:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-24 20:25:59 +01:00
|
|
|
|
2023-07-06 19:48:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-05-08 19:02:15 +03:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-05-08 19:02:15 +03:00
|
|
|
|
2020-08-20 10:08:27 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2022-02-05 22:18:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-05 14:47:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-06 21:38:11 +01:00
|
|
|
|
|
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2021-04-22 18:07:46 -07:00
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
std: Handle field struct defaults in std.mem.zeroInit
I originally started monkeying with this because std.mem.zeroes doesn't support sentinel-terminated const slices even with defaults in 0.10.x.
I see that std.mem.zeroes was modified in #13256 to allow setting these slices to "".
That got me partway to where I wanted, but there was still an issue fields whose types are structs, they wouldn't get their defaults.
So when iterating struct fields looking for default values, when there is no default value and the type is .Struct, it will delegate to a call to zeroInit.
* Initialize struct fields in zeroInit exactly once
In my changes, similar to the previous implementation, the priority order for fields being initialized is:
1. If the `init` argument is a tuple, the nth element corresponding to the nth field of the struct.
2. Otherwise, if the `init` argument is not a tuple, try to find a matching field name on `init` and use that field.
3. Is the field has a default value, initalize with that value.
4. Fall back to what the field would have been initialized to via a recursive call to `std.mem.zeroInit`.
But instead of initializing a default instance of the struct and then running multiple passes over it, the init method is chosen per-field and each field is initialized exactly once.
2023-01-16 04:24:47 -08:00
|
|
|
|
|
|
|
|
|
2023-04-30 18:02:08 +01:00
|
|
|
|
std: Handle field struct defaults in std.mem.zeroInit
I originally started monkeying with this because std.mem.zeroes doesn't support sentinel-terminated const slices even with defaults in 0.10.x.
I see that std.mem.zeroes was modified in #13256 to allow setting these slices to "".
That got me partway to where I wanted, but there was still an issue fields whose types are structs, they wouldn't get their defaults.
So when iterating struct fields looking for default values, when there is no default value and the type is .Struct, it will delegate to a call to zeroInit.
* Initialize struct fields in zeroInit exactly once
In my changes, similar to the previous implementation, the priority order for fields being initialized is:
1. If the `init` argument is a tuple, the nth element corresponding to the nth field of the struct.
2. Otherwise, if the `init` argument is not a tuple, try to find a matching field name on `init` and use that field.
3. Is the field has a default value, initalize with that value.
4. Fall back to what the field would have been initialized to via a recursive call to `std.mem.zeroInit`.
But instead of initializing a default instance of the struct and then running multiple passes over it, the init method is chosen per-field and each field is initialized exactly once.
2023-01-16 04:24:47 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
2023-05-15 09:51:00 +08:00
|
|
|
|
std: Handle field struct defaults in std.mem.zeroInit
I originally started monkeying with this because std.mem.zeroes doesn't support sentinel-terminated const slices even with defaults in 0.10.x.
I see that std.mem.zeroes was modified in #13256 to allow setting these slices to "".
That got me partway to where I wanted, but there was still an issue fields whose types are structs, they wouldn't get their defaults.
So when iterating struct fields looking for default values, when there is no default value and the type is .Struct, it will delegate to a call to zeroInit.
* Initialize struct fields in zeroInit exactly once
In my changes, similar to the previous implementation, the priority order for fields being initialized is:
1. If the `init` argument is a tuple, the nth element corresponding to the nth field of the struct.
2. Otherwise, if the `init` argument is not a tuple, try to find a matching field name on `init` and use that field.
3. Is the field has a default value, initalize with that value.
4. Fall back to what the field would have been initialized to via a recursive call to `std.mem.zeroInit`.
But instead of initializing a default instance of the struct and then running multiple passes over it, the init method is chosen per-field and each field is initialized exactly once.
2023-01-16 04:24:47 -08:00
|
|
|
|
2023-02-18 09:02:57 -07:00
|
|
|
|
std: Handle field struct defaults in std.mem.zeroInit
I originally started monkeying with this because std.mem.zeroes doesn't support sentinel-terminated const slices even with defaults in 0.10.x.
I see that std.mem.zeroes was modified in #13256 to allow setting these slices to "".
That got me partway to where I wanted, but there was still an issue fields whose types are structs, they wouldn't get their defaults.
So when iterating struct fields looking for default values, when there is no default value and the type is .Struct, it will delegate to a call to zeroInit.
* Initialize struct fields in zeroInit exactly once
In my changes, similar to the previous implementation, the priority order for fields being initialized is:
1. If the `init` argument is a tuple, the nth element corresponding to the nth field of the struct.
2. Otherwise, if the `init` argument is not a tuple, try to find a matching field name on `init` and use that field.
3. Is the field has a default value, initalize with that value.
4. Fall back to what the field would have been initialized to via a recursive call to `std.mem.zeroInit`.
But instead of initializing a default instance of the struct and then running multiple passes over it, the init method is chosen per-field and each field is initialized exactly once.
2023-01-16 04:24:47 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-03-28 12:10:36 +01:00
|
|
|
|
std: Handle field struct defaults in std.mem.zeroInit
I originally started monkeying with this because std.mem.zeroes doesn't support sentinel-terminated const slices even with defaults in 0.10.x.
I see that std.mem.zeroes was modified in #13256 to allow setting these slices to "".
That got me partway to where I wanted, but there was still an issue fields whose types are structs, they wouldn't get their defaults.
So when iterating struct fields looking for default values, when there is no default value and the type is .Struct, it will delegate to a call to zeroInit.
* Initialize struct fields in zeroInit exactly once
In my changes, similar to the previous implementation, the priority order for fields being initialized is:
1. If the `init` argument is a tuple, the nth element corresponding to the nth field of the struct.
2. Otherwise, if the `init` argument is not a tuple, try to find a matching field name on `init` and use that field.
3. Is the field has a default value, initalize with that value.
4. Fall back to what the field would have been initialized to via a recursive call to `std.mem.zeroInit`.
But instead of initializing a default instance of the struct and then running multiple passes over it, the init method is chosen per-field and each field is initialized exactly once.
2023-01-16 04:24:47 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-06-01 14:47:18 -04:00
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-01 00:33:35 +03:00
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
|
|
|
|
|
2020-06-01 14:47:18 -04:00
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-06-01 14:47:18 -04:00
|
|
|
|
2020-07-01 00:33:35 +03:00
|
|
|
|
2020-07-16 16:00:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-16 23:35:31 +03:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-07-16 16:00:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-28 12:10:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
std: Handle field struct defaults in std.mem.zeroInit
I originally started monkeying with this because std.mem.zeroes doesn't support sentinel-terminated const slices even with defaults in 0.10.x.
I see that std.mem.zeroes was modified in #13256 to allow setting these slices to "".
That got me partway to where I wanted, but there was still an issue fields whose types are structs, they wouldn't get their defaults.
So when iterating struct fields looking for default values, when there is no default value and the type is .Struct, it will delegate to a call to zeroInit.
* Initialize struct fields in zeroInit exactly once
In my changes, similar to the previous implementation, the priority order for fields being initialized is:
1. If the `init` argument is a tuple, the nth element corresponding to the nth field of the struct.
2. Otherwise, if the `init` argument is not a tuple, try to find a matching field name on `init` and use that field.
3. Is the field has a default value, initalize with that value.
4. Fall back to what the field would have been initialized to via a recursive call to `std.mem.zeroInit`.
But instead of initializing a default instance of the struct and then running multiple passes over it, the init method is chosen per-field and each field is initialized exactly once.
2023-01-16 04:24:47 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add initialization helper
When using C libraries, C99 designator list initialization is often
times used to initialize data structure.
While `std.mem.zeroes` and manually assigning to each field can
achieve the same result, it is much more verbose then the equivalent
C code:
```zig
usingnamespace @cImport({
@cInclude("sokol_app.h");
});
// Using `std.mem.zeroes` and manual assignment.
var app_desc = std.mem.zeroes(sapp_desc);
app_desc.init_cb = init;
app_desc.frame_cb = frame;
app_desc.cleanup_cb = cleanup;
app_desc.width = 400;
app_desc.height = 300;
app_desc.window_name = "no default init";
// Using `std.mem.defaultInit`.
var app_desc = std.mem.defaultInit(sapp_desc, .{
.init_cb = init,
.frame_cb = frame,
.cleanup_cb = cleanup,
.width = 400,
.height = 300,
.window_name = "default init"
});
```
The `std.mem.defaultInit` aims to solve this problem by zero
initializing all fields of the given struct to their zero, or default
value if any. Each field mentionned in the `init` variable is then
assigned to the corresponding field in the struct.
If a field is a struct, and an initializer for it is present, it is
recursively initialized.
2020-05-29 18:25:21 -04:00
|
|
|
|
|
|
|
|
|
2023-05-23 15:33:12 +03:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-12 17:39:25 +02:00
|
|
|
|
2020-01-01 18:08:40 -05:00
|
|
|
|
2023-06-02 22:02:45 -04:00
|
|
|
|
2023-06-19 12:05:40 -07:00
|
|
|
|
|
|
|
|
|
2020-01-01 18:08:40 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-07 05:30:54 -07:00
|
|
|
|
2016-08-11 22:25:13 -07:00
|
|
|
|
2020-01-01 18:08:40 -05:00
|
|
|
|
2018-08-07 05:30:54 -07:00
|
|
|
|
|
|
|
|
|
2023-06-25 21:33:55 +06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-06-25 21:33:55 +06:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-06-25 21:33:55 +06:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-06-25 21:33:55 +06:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-06-25 21:33:55 +06:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-06-25 21:33:55 +06:00
|
|
|
|
2018-08-07 05:30:54 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-01 18:08:40 -05:00
|
|
|
|
2017-12-15 17:26:22 -05:00
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-08-11 22:25:13 -07:00
|
|
|
|
2016-09-23 02:00:23 -04:00
|
|
|
|
2017-02-07 17:19:51 -05:00
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2017-02-07 17:19:51 -05:00
|
|
|
|
2019-09-03 23:56:04 +02:00
|
|
|
|
2023-02-23 16:18:15 -07:00
|
|
|
|
|
|
|
|
|
2017-02-07 17:19:51 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-09 13:53:20 +11:00
|
|
|
|
2020-04-29 14:09:12 +03:00
|
|
|
|
|
|
|
|
|
2023-06-02 22:02:45 -04:00
|
|
|
|
2020-03-09 13:53:20 +11:00
|
|
|
|
2020-04-29 14:09:12 +03:00
|
|
|
|
2020-03-09 13:53:20 +11:00
|
|
|
|
|
|
|
|
|
2020-04-29 14:09:12 +03:00
|
|
|
|
2020-03-09 13:53:20 +11:00
|
|
|
|
|
|
|
|
|
2020-04-29 14:09:12 +03:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-09 13:53:20 +11:00
|
|
|
|
|
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-05 12:26:26 -05:00
|
|
|
|
2020-03-30 21:56:09 +11:00
|
|
|
|
|
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
2020-03-30 21:56:09 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2020-03-30 21:56:09 +11:00
|
|
|
|
|
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
|
|
|
|
|
2020-03-30 21:56:09 +11:00
|
|
|
|
|
|
|
|
|
2022-02-01 11:42:41 -07:00
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
|
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
|
|
|
|
|
2023-04-30 18:02:08 +01:00
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2020-04-01 01:44:14 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-30 21:56:09 +11:00
|
|
|
|
2020-04-01 01:44:14 +11:00
|
|
|
|
2020-03-01 13:21:29 -05:00
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-16 21:41:46 -04:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
|
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 11:42:41 -07:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-01-22 17:28:29 -05:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-05-06 18:33:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
|
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
|
|
|
|
|
2021-03-05 22:08:34 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
|
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
|
|
|
|
|
2020-03-01 13:21:29 -05:00
|
|
|
|
2023-01-22 16:40:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-19 19:30:09 -04:00
|
|
|
|
|
|
|
|
|
2020-03-01 13:07:55 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-26 22:59:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-20 00:36:05 +01:00
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-20 00:36:05 +01:00
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-20 00:36:05 +01:00
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2018-01-17 01:50:35 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-17 01:50:35 -05:00
|
|
|
|
|
|
|
|
|
2017-04-05 17:55:50 -04:00
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2017-10-06 00:27:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2017-10-06 00:27:15 -04:00
|
|
|
|
|
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
2017-04-05 17:55:50 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2017-10-13 09:31:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2017-10-13 09:31:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
2017-10-13 09:31:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-10 09:47:58 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2017-10-06 00:27:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
2020-10-17 19:23:37 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
2018-05-30 16:09:11 -04:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-10-17 19:23:37 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-06 00:27:15 -04:00
|
|
|
|
2017-04-19 01:13:15 -04:00
|
|
|
|
2017-05-03 18:12:07 -04:00
|
|
|
|
2018-05-30 16:09:11 -04:00
|
|
|
|
2017-04-19 01:13:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-05 14:25:44 +02:00
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-05 21:15:44 +02:00
|
|
|
|
2022-10-18 14:49:09 +02:00
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-05 14:25:44 +02:00
|
|
|
|
2020-09-05 11:24:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-05 21:15:44 +02:00
|
|
|
|
2022-10-18 14:49:09 +02:00
|
|
|
|
2020-09-05 11:24:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 14:49:09 +02:00
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
2022-10-18 14:49:09 +02:00
|
|
|
|
2020-10-17 19:23:37 -07:00
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
2020-09-05 16:55:32 +02:00
|
|
|
|
|
|
|
|
|
2020-09-05 11:46:41 +02:00
|
|
|
|
2020-10-24 03:49:04 +02:00
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
2020-09-05 11:46:41 +02:00
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
|
|
|
|
|
2020-09-05 11:24:05 +02:00
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-22 05:34:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
2020-09-05 11:22:12 +02:00
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
2022-10-18 14:49:09 +02:00
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2020-09-05 16:55:32 +02:00
|
|
|
|
2021-11-26 02:56:38 +01:00
|
|
|
|
2020-09-05 11:46:41 +02:00
|
|
|
|
2020-09-06 16:23:18 +02:00
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
2020-09-05 11:46:41 +02:00
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-05 11:24:05 +02:00
|
|
|
|
2020-09-05 15:31:22 +02:00
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
2021-05-22 05:34:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
2017-04-19 01:13:15 -04:00
|
|
|
|
2020-09-05 11:22:12 +02:00
|
|
|
|
2017-04-19 01:13:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-05 14:17:38 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-09-05 16:55:32 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-19 01:13:15 -04:00
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-05-22 05:34:49 -04:00
|
|
|
|
2022-10-18 14:49:09 +02:00
|
|
|
|
2021-06-01 18:35:13 +09:00
|
|
|
|
2021-05-22 05:34:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 14:49:09 +02:00
|
|
|
|
2021-06-01 18:35:13 +09:00
|
|
|
|
2021-05-22 05:34:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-11-26 02:56:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 16:47:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-24 16:47:44 +01:00
|
|
|
|
|
|
|
|
|
2021-01-06 23:56:02 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-06 23:56:02 +00:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2021-01-06 23:56:02 +00:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2021-01-06 23:56:02 +00:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2021-01-06 23:56:02 +00:00
|
|
|
|
|
|
|
|
|
2018-12-13 06:38:14 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2018-12-13 06:38:14 -05:00
|
|
|
|
|
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
2018-12-13 06:38:14 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
2018-12-13 06:38:14 -05:00
|
|
|
|
2023-02-18 09:02:57 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2018-12-13 06:38:14 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-15 13:14:16 +06:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-18 09:02:57 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2022-08-21 17:24:04 +03:00
|
|
|
|
2017-11-30 11:20:39 -07:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2019-02-15 18:05:50 -05:00
|
|
|
|
2020-03-19 14:48:47 -04:00
|
|
|
|
2017-11-30 11:20:39 -07:00
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-21 17:24:04 +03:00
|
|
|
|
2018-11-14 21:40:53 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2019-02-15 18:05:50 -05:00
|
|
|
|
2020-03-19 14:48:47 -04:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2018-12-16 12:03:37 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-16 12:03:37 -05:00
|
|
|
|
2018-12-17 11:05:50 -05:00
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-17 11:05:50 -05:00
|
|
|
|
2018-12-16 12:03:37 -05:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2023-04-18 20:18:23 -04:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-28 01:04:26 +02:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-03 09:00:39 -05:00
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2022-08-21 17:24:04 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-17 00:59:31 -04:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-17 00:59:31 -04:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-09-12 05:52:15 -05:00
|
|
|
|
2023-04-27 17:26:16 -07:00
|
|
|
|
2021-09-12 05:52:15 -05:00
|
|
|
|
2023-04-27 17:26:16 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-09-12 05:52:15 -05:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2020-10-17 14:09:59 +02:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2018-11-07 20:50:10 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-09-12 05:52:15 -05:00
|
|
|
|
2023-04-27 17:26:16 -07:00
|
|
|
|
2021-09-12 05:52:15 -05:00
|
|
|
|
2023-04-27 17:26:16 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-09-12 05:52:15 -05:00
|
|
|
|
|
|
|
|
|
2020-03-10 23:50:04 +01:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2020-10-17 14:09:59 +02:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-09-03 18:09:55 +03:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-24 23:04:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2023-04-18 20:18:23 -04:00
|
|
|
|
|
|
|
|
|
2018-11-07 20:50:10 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-11-07 20:50:10 -05:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-11-07 20:50:10 -05:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-11-07 20:50:10 -05:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-11-07 20:50:10 -05:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-11-07 20:50:10 -05:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2017-04-04 01:52:20 -04:00
|
|
|
|
|
|
|
|
|
2021-06-24 23:29:39 +01:00
|
|
|
|
2023-04-30 18:02:08 +01:00
|
|
|
|
2022-01-24 21:40:19 +01:00
|
|
|
|
|
|
|
|
|
2021-06-24 23:29:39 +01:00
|
|
|
|
2023-05-17 02:10:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-24 23:29:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-01-24 21:40:19 +01:00
|
|
|
|
2021-06-24 23:29:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-17 02:10:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-24 23:29:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-17 02:10:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-01-24 21:40:19 +01:00
|
|
|
|
2023-05-17 02:10:44 +03:00
|
|
|
|
2021-06-24 23:29:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-17 02:10:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-24 23:29:39 +01:00
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
2017-10-06 00:27:15 -04:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
|
|
|
|
|
2019-02-04 15:24:06 -05:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2017-04-04 01:52:20 -04:00
|
|
|
|
2017-10-06 00:27:15 -04:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2017-12-22 00:50:30 -05:00
|
|
|
|
2017-04-04 01:52:20 -04:00
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2022-06-24 17:24:44 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2022-06-24 17:24:44 +02:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2022-06-24 17:24:44 +02:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2022-06-24 17:24:44 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-24 17:24:44 +02:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-30 02:17:15 +09:00
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-03-20 23:28:02 +00:00
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-03-20 23:28:02 +00:00
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
|
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
|
|
|
|
|
2019-02-04 15:24:06 -05:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
2019-02-04 15:24:06 -05:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
|
|
|
|
|
2019-02-04 15:24:06 -05:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
2023-07-10 11:34:39 -07:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-10 11:34:39 -07:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-10 11:34:39 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
2023-07-10 11:34:39 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2018-11-30 02:17:15 +09:00
|
|
|
|
2018-11-26 01:09:12 +09:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-26 13:26:46 +02:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-26 13:26:46 +02:00
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2017-04-29 19:23:33 -04:00
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-26 13:26:46 +02:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
2022-07-26 13:26:46 +02:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-26 13:26:46 +02:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-26 13:26:46 +02:00
|
|
|
|
|
|
|
|
|
2022-12-10 13:57:50 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
2017-04-06 05:34:04 -04:00
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-30 16:09:11 -04:00
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-04-24 20:50:21 -04:00
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2017-04-04 01:52:20 -04:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2017-04-04 01:52:20 -04:00
|
|
|
|
2022-06-24 17:24:44 +02:00
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2022-06-24 17:24:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-06 00:27:15 -04:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
2022-06-24 17:24:44 +02:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
2017-10-06 00:27:15 -04:00
|
|
|
|
2017-04-04 01:52:20 -04:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
2019-02-07 10:55:23 -05:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-04 15:24:06 -05:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 17:49:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-10 11:34:39 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-26 13:26:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-06 01:53:07 -07:00
|
|
|
|
|
|
|
|
|
2019-02-04 15:24:06 -05:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-25 21:04:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
2023-05-06 21:47:56 -07:00
|
|
|
|
2023-05-04 18:19:31 -07:00
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-26 13:26:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mem: add splitBackwards (#11908)
* mem: refactor tests of split()
- add a few cases for .rest()
- use expectEqualSlices()
* mem: add splitBackwards
Over the last couple of weeks weeks I needed to iterate over a
collection backwards at least twice. Do we want to have this in stdlib?
If yes, click "Merge" and start using today! Free shipping and returns
(before 1.0).
Why is this useful?
-------------------
I need this for building an error wrapper: errors are added in the
wrapper from "lowest" level to "highest" level, and then printed in
reverse order. Imagine `UpdateUsers` call, which needs to return
`error.InvalidInput` and a wrappable error context. In Go we would add a
context to the error when returning it:
// if update_user fails, add context on which user we are operating
if err := update_user(user); err != nil {
return fmt.Errorf("user id=%d: %w", user.id, err)
}
Since Zig cannot pass anything else than u16 with an error (#2647), I
will pass a `err_ctx: *Err`, to the callers, where they can, besides
returning an error, augment it with auxiliary data. `Err` is a
preallocated array that can add zero-byte-separated strings. For a
concrete example, imagine such a call graph:
update_user(User, *Err) error{InvalidInput}!<...>
validate_user([]const u8, *Err) error{InvalidInput}!<...>
Where `validate_user` would like, besides only the error, signal the
invalid field. And `update_user`, besides the error, would signal the
offending user id.
We also don't want the low-level functions to know in which context they
are operating to construct a meaningful error message: if validation
fails, they append their "context" to the buffer. To translate/augment
the Go example above:
pub fn validate_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
const name = user.name;
if (!ascii.isAlpha(name)) {
err_ctx.print("name '{s}' must be ascii-letters only", .{name});
return error.InvalidInput;
}
<...>
}
// update_user validates each user and does something with it.
pub fn update_user(err_ctx: *Err, user: User) error{InvalidInput}!void {
// validate the user before updating it
validate_user(user) catch {
err_ctx.print("user id={d}", .{user.id});
return error.InvalidInput;
};
<...>
}
Then the top-level function (in my case, CLI) will read the buffer
backwards (splitting on `"\x00"`) and print:
user id=123: name 'Žvangalas' must be ascii-letters only
To read that buffer backwards, dear readers of this commit message, I
need `mem.splitBackwards`.
2022-06-29 09:23:09 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-07 00:42:41 -05:00
|
|
|
|
2017-05-28 15:54:53 +02:00
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2020-07-08 23:07:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2020-07-08 23:07:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2021-01-26 22:40:34 +11:00
|
|
|
|
2017-05-28 15:54:53 +02:00
|
|
|
|
2019-02-07 00:42:41 -05:00
|
|
|
|
|
|
|
|
|
2020-07-08 23:07:44 +02:00
|
|
|
|
|
|
|
|
|
2019-02-07 00:42:41 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-23 23:08:09 -05:00
|
|
|
|
2017-05-28 15:54:53 +02:00
|
|
|
|
2019-02-07 10:55:23 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-28 15:54:53 +02:00
|
|
|
|
|
|
|
|
|
2020-07-08 23:07:44 +02:00
|
|
|
|
|
|
|
|
|
2019-02-07 00:42:41 -05:00
|
|
|
|
|
|
|
|
|
2017-05-28 15:54:53 +02:00
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-01-26 22:40:34 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2021-01-26 22:40:34 +11:00
|
|
|
|
2020-02-14 19:15:09 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-14 19:15:09 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-14 19:15:09 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-14 19:15:09 +11:00
|
|
|
|
2017-05-28 15:54:53 +02:00
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-01-26 22:40:34 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2021-01-26 22:40:34 +11:00
|
|
|
|
2020-07-08 23:07:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-07-08 23:07:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-07-08 23:07:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-07-08 23:07:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-17 00:03:16 -04:00
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2022-04-17 11:43:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-17 00:03:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-04-17 11:43:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-17 00:03:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-04-17 11:43:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-17 00:03:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-14 19:15:09 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-14 19:15:09 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-14 19:15:09 +11:00
|
|
|
|
2022-04-17 11:43:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-17 00:03:16 -04:00
|
|
|
|
|
|
|
|
|
2017-03-16 16:02:35 -04:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-07 17:19:51 -05:00
|
|
|
|
|
|
|
|
|
2017-03-16 16:02:35 -04:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-06-05 14:29:28 +06:00
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2019-06-09 19:24:24 -04:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-08 14:45:21 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2021-05-08 14:45:21 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2016-09-23 02:00:23 -04:00
|
|
|
|
2019-06-09 19:24:24 -04:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2016-09-23 02:00:23 -04:00
|
|
|
|
|
|
|
|
|
2019-06-09 19:24:24 -04:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2016-09-23 02:00:23 -04:00
|
|
|
|
2017-11-30 11:20:39 -07:00
|
|
|
|
2019-06-09 19:24:24 -04:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-11-30 11:20:39 -07:00
|
|
|
|
2016-09-23 02:00:23 -04:00
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2023-04-27 17:26:16 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-06-05 14:29:28 +06:00
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-08-23 09:03:02 +09:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-08-23 09:03:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-08-23 09:03:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-08-23 09:03:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-23 09:03:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-08-23 09:03:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-23 09:03:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
2021-05-22 14:03:06 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-09-12 05:52:15 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-12 17:22:35 -05:00
|
|
|
|
2017-04-04 01:52:20 -04:00
|
|
|
|
2020-07-12 17:39:25 +02:00
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
2017-05-06 23:13:12 -04:00
|
|
|
|
2017-12-15 11:15:58 -05:00
|
|
|
|
2023-06-02 22:02:45 -04:00
|
|
|
|
2017-05-06 23:13:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-06 23:13:12 -04:00
|
|
|
|
|
|
|
|
|
2020-07-12 17:39:25 +02:00
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
2017-05-06 23:13:12 -04:00
|
|
|
|
2017-12-15 11:15:58 -05:00
|
|
|
|
2023-06-02 22:02:45 -04:00
|
|
|
|
2017-05-06 23:13:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-22 14:38:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-02 22:02:45 -04:00
|
|
|
|
|
|
|
|
|
2021-10-22 14:38:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-10-22 14:38:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-18 09:02:57 -07:00
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-18 09:02:57 -07:00
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-10-08 00:37:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-06 23:13:12 -04:00
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
2021-10-22 14:38:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-18 09:02:57 -07:00
|
|
|
|
2021-10-22 14:38:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-09 15:44:08 -07:00
|
|
|
|
2021-10-22 14:38:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-06 23:13:12 -04:00
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
2018-05-31 10:56:59 -04:00
|
|
|
|
2018-04-30 20:35:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2019-11-27 03:30:39 -05:00
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
|
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
2023-03-31 22:50:31 +02:00
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-31 22:50:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-31 22:50:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-31 22:50:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-31 22:48:32 +02:00
|
|
|
|
2022-12-02 12:04:50 -07:00
|
|
|
|
|
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
|
|
|
|
|
2018-01-25 04:10:11 -05:00
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2019-11-27 03:30:39 -05:00
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2017-12-14 19:41:35 -05:00
|
|
|
|
2018-03-07 03:55:52 -05:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
2022-11-05 16:55:50 -05:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-22 04:55:28 -04:00
|
|
|
|
2023-04-26 13:57:08 -07:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
2023-04-30 18:02:08 +01:00
|
|
|
|
2021-01-03 04:19:24 -07:00
|
|
|
|
2023-02-18 09:02:57 -07:00
|
|
|
|
2021-01-03 04:19:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-06 23:55:33 -07:00
|
|
|
|
2021-01-03 04:19:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-06 23:55:33 -07:00
|
|
|
|
|
|
|
|
|
2021-05-31 15:57:48 +09:00
|
|
|
|
2021-01-06 23:55:33 -07:00
|
|
|
|
|
|
|
|
|
2021-01-03 04:19:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-20 23:23:10 -06:00
|
|
|
|
2021-01-03 04:19:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
2021-05-22 04:55:28 -04:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
|
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2021-04-25 16:16:24 -07:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-29 00:37:25 +01:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 15:27:00 -07:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
2021-07-02 15:27:00 -07:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
2021-07-02 15:27:00 -07:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-07-25 19:38:26 -04:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
2022-08-21 17:24:04 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2018-03-07 03:55:52 -05:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2022-08-21 17:24:04 +03:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2018-03-07 03:55:52 -05:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2018-03-07 03:55:52 -05:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2018-03-07 03:55:52 -05:00
|
|
|
|
|
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
2022-08-21 17:24:04 +03:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2022-08-21 17:24:04 +03:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
2018-12-12 20:19:46 -05:00
|
|
|
|
2018-03-07 03:55:52 -05:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
2021-06-06 18:05:06 -07:00
|
|
|
|
|
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2022-12-18 21:57:18 -05:00
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-15 13:14:16 +06:00
|
|
|
|
2022-12-21 16:40:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-21 16:40:30 +02:00
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
2023-06-15 13:14:16 +06:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
2023-06-15 13:14:16 +06:00
|
|
|
|
2021-06-06 11:12:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
|
|
|
|
|
2022-02-01 11:42:41 -07:00
|
|
|
|
2022-02-01 18:10:19 -07:00
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-30 02:54:03 +02:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2020-03-18 20:35:19 -04:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2020-03-18 20:35:19 -04:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2019-11-06 23:25:57 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2019-11-06 23:25:57 -05:00
|
|
|
|
2023-02-18 09:02:57 -07:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2018-11-13 05:08:37 -08:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2018-11-13 05:08:37 -08:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-11 20:39:05 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-16 17:15:52 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
2020-11-16 12:50:05 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
2020-07-12 17:39:25 +02:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2019-11-06 23:25:57 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2019-11-06 23:25:57 -05:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
2019-11-23 04:45:35 -05:00
|
|
|
|
2019-11-19 20:29:08 -05:00
|
|
|
|
2023-04-14 17:29:40 +01:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
2020-07-12 17:39:25 +02:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2019-11-06 23:25:57 -05:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2019-11-19 20:29:08 -05:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2018-11-13 05:08:37 -08:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2018-11-13 05:08:37 -08:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-11 20:39:05 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-11-19 20:29:08 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
2020-11-16 12:50:05 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
2020-07-12 17:39:25 +02:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2019-11-19 20:29:08 -05:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2021-04-12 16:43:50 -07:00
|
|
|
|
2020-02-25 21:29:56 +01:00
|
|
|
|
|
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2018-10-19 23:27:16 +02:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2018-10-19 16:19:22 -05:00
|
|
|
|
|
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
2020-03-17 17:33:44 -04:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-17 17:33:44 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-17 17:33:44 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-17 17:33:44 -04:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
2020-03-17 17:33:44 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-05 14:29:28 +06:00
|
|
|
|
2020-03-17 17:33:44 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-05 14:29:28 +06:00
|
|
|
|
2020-03-17 17:33:44 -04:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
2020-11-16 12:50:05 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2020-07-11 14:09:04 +03:00
|
|
|
|
2020-03-17 18:54:09 -04:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
2020-03-17 18:54:09 -04:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2021-05-08 14:45:21 -07:00
|
|
|
|
2020-02-20 20:01:52 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-25 15:07:35 -05:00
|
|
|
|
2020-03-10 23:50:04 +01:00
|
|
|
|
2020-02-25 15:07:35 -05:00
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-25 15:07:35 -05:00
|
|
|
|
|
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-11 20:39:05 -07:00
|
|
|
|
|
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2023-06-05 14:29:28 +06:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-23 18:03:50 +01:00
|
|
|
|
|
|
|
|
|
2020-11-16 12:50:05 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-12 03:13:46 +01:00
|
|
|
|
|
|
|
|
|
2022-08-24 01:35:45 +02:00
|
|
|
|
2019-06-27 22:23:09 +01:00
|
|
|
|
2022-10-30 16:10:20 -07:00
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-22 23:42:58 -04:00
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
|
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
2019-02-06 13:48:04 -05:00
|
|
|
|
2020-08-25 22:43:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-09 18:22:50 +01:00
|
|
|
|
2020-08-26 01:48:51 +02:00
|
|
|
|
2022-12-09 18:22:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-15 13:14:16 +06:00
|
|
|
|
|
|
|
|
|
2022-12-09 18:22:50 +01:00
|
|
|
|
|
|
|
|
|
2022-12-13 21:58:03 -05:00
|
|
|
|
2022-12-09 18:22:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-13 21:58:03 -05:00
|
|
|
|
2022-12-09 18:22:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-13 21:58:03 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-09 18:22:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-13 21:58:03 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-12-13 21:58:03 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-09 18:22:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-25 22:43:42 +02:00
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-06 13:48:04 -05:00
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2022-08-24 01:35:45 +02:00
|
|
|
|
2020-06-26 19:29:06 -06:00
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
2022-12-18 21:57:18 -05:00
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-24 01:35:45 +02:00
|
|
|
|
2019-06-27 22:23:09 +01:00
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
2022-12-18 21:57:18 -05:00
|
|
|
|
2020-04-24 15:36:08 -04:00
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
|
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2022-12-18 21:57:18 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-18 21:57:18 -05:00
|
|
|
|
2020-04-17 14:15:36 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-27 22:22:17 +01:00
|
|
|
|
2019-06-27 22:23:09 +01:00
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2020-05-14 16:34:04 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-04 20:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-26 19:56:37 -04:00
|
|
|
|
2020-02-25 15:07:35 -05:00
|
|
|
|
|
|
|
|
|
2021-11-30 00:13:07 -07:00
|
|
|
|
2020-02-25 15:07:35 -05:00
|
|
|
|
|
|
|
|
|
2020-12-23 22:10:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-27 01:07:35 -07:00
|
|
|
|
2020-12-23 22:10:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-30 02:54:03 +02:00
|
|
|
|
2020-12-23 22:10:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-15 13:14:16 +06:00
|
|
|
|
2020-12-23 22:10:28 +01:00
|
|
|
|
|
|
|
|
|
2023-06-09 16:02:18 -07:00
|
|
|
|
2020-12-23 22:10:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-12-23 22:10:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2020-12-23 22:10:28 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
2023-04-18 20:18:23 -04:00
|
|
|
|
|
|
|
|
|
2022-10-19 12:14:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
|
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-05 14:29:28 +06:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
2023-06-22 18:46:56 +01:00
|
|
|
|
2022-10-18 11:33:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|