On Wed, 11 Feb 2026 12:19:04 +0100 "Danilo Krummrich" <[email protected]> wrote:
> On Wed Feb 11, 2026 at 12:07 PM CET, Boris Brezillon wrote: > > I try to avoid using concepts the language I rely on is not friendly > > with. > > It's not really a language limitation. For instance, you can implement lists > the > exact same way as they can be implemented in C. It's more that a memory safe > list implementation is quite tricky in general. That's what I mean by trickier to use, they are because of rust safety. And again, that's not a case for saying "nah, rust is not a good fit, it can't do easy-to-use-lists", but rather a good opportunity to think twice about the containers we want to use. > > Lists clearly do have their place. In this specific case, it probably doesn't > matter too much, but in general I'd abstain from not using a list (where it is > the best fit) just because they are tricky in getting them implemented in a > memory safe way. Read my other reply. I'm not saying "don't ever use a list in rust!", I'm saying, "if there are valid alternatives, and they make things slightly simpler, why not use these alternatives". And that's the case here I think, especially since the C side does exactly that (using an xarray over a list). Note how I didn't mention the list under the JobQueue, because for that one, I'm not too sure XArray is a good fit (jobs might be moved around between lists depending on their progress at some point).
