@d-e-s-o @ work
@d-e-s-o @ work
Would it be possible to cut another release or when is the next one scheduled? I am specifically interested in having https://github.com/bheisler/criterion.rs/pull/705 available.
The skeleton-based accessors (`bss`, `rodata`, ...) tend to conflict with other reasonable-to-call methods, such as `maps()`. For example, from `capable`: ```rust impl OpenCapableSkel { OpenCapableProgs { inner: &self.obj } }...
(there is some potential overlap with https://github.com/libbpf/libbpf-rs/issues/602 and perhaps even https://github.com/libbpf/libbpf-rs/issues/590, depending on what we end up building, but let's perhaps capture issues as we identify them currently) There may...
Sort of orthogonal to https://github.com/libbpf/libbpf-rs/issues/602, we also got a generic request to include `enum` types in the set of types generated. Reasoning: > they aren't often referenced from types explicitly...
We need to generate Rust types for types used in bpf maps. Currently we lack any such generation and that's causing folks to have to resort to using `bindgen` out-of-band,...
We got some feedback that the documentation we have is generally not the greatest. - [ ] the belief is that more examples showing best practices and common patterns would...
We should consider introducing a proper `enum` for tracepoint categories. Relying on a textual representation seems...icky.
`RingBuffer` (and `Map`) objects are not the easiest to use. One request we had come up more than once now is that it may prove beneficial to user acceptance to...
In response to https://github.com/libbpf/libbpf-rs/issues/500 I created https://github.com/danielocfb/libbpf-sys/commit/5e93a20fecc8ca9e9823449d8e8ea388003511d2 to make sure that `libbpf-sys` is also tested in a 32 bit setting. That seems to blow up pretty prominently immediately: https://github.com/danielocfb/libbpf-sys/actions/runs/5479871661/jobs/9982296567 ```...