Re: [RFC PATCH 3/4] rust/drm: Add DRM Jobqueue

[Boris Brezillon <boris.brezillon@collabora.com>]

On Wed, 11 Feb 2026 13:32:26 +0100
"Danilo Krummrich" <dakr@kernel.org> wrote:

> On Wed Feb 11, 2026 at 1:10 PM CET, Boris Brezillon wrote:
> > On Wed, 11 Feb 2026 12:19:04 +0100
> > "Danilo Krummrich" <dakr@kernel.org> 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.  
> 
> Yeah, we agree on this. What I don't agree with is the "avoid using concepts"
> part, because it came across in an unconditional way.

Well, I guess that's me approaching problems differently then. I
usually consider that, if a language makes my life harder to do
something, there are good reasons, and there's probably alternatives
(with different paradigms) to do the same thing. At least that's my
first reaction. It might be that after further investigation, that's
just how it is, and I have to live with the extra complexity. But yeah,
I stand to my original statement: if something is complex, I'll always
investigate other options before going for the hard way.

> 
> > 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.  
> 
> I think I never implied that you were saying anything along the lines of "rust
> is not a good fit" in any way. No idea where this comes from. :)

That one was more referring to Philipp's reply, where he was saying
some people dismiss rust because of lists, and I wanted to make it
clear that's not what this about here.