Meghan Denny
Meghan Denny
are you perhaps looking for [std.io.BufferedReader](https://ziglang.org/documentation/master/std/#std.io.BufferedReader) and [std.io.BufferedWriter](https://ziglang.org/documentation/master/std/#std.io.BufferedWriter) ?
in that case it sounds like [std.BoundedArray](https://ziglang.org/documentation/master/std/#std.BoundedArray) and [std.fifo.LinearFifo](https://ziglang.org/documentation/master/std/#std.fifo.LinearFifo) ?
@dylan-conway do you remember if we filed an upstream bug for this yet?
https://bugs.webkit.org/show_bug.cgi?id=295660
OpenTracing is now https://opentelemetry.io/ Spec: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/overview.md Go Client: https://pkg.go.dev/go.opentelemetry.io/otel/[email protected] Example: https://github.com/open-telemetry/opentelemetry-go/blob/master/example/basic/main.go
`std.testing.expectEqualStrings()` is currently unusable as of this edit: the test part works, specifically the debugging output that makes it more useful than `expect(std.mem.eql(a, b))`
afaik changing the behavior is planned, but its because unit tests are not supposed to have side effects and using `std.log` does still work
`min_per_day` and `min_per_week` are both very context and calendar specific `min_per_hour` is needed rare enough, along with what truemedian said, i dont think is a strong argument for it to...
this is blocking the `ava` test runner
shouldnt it compile error since the result type isnt a function pointer?