But it does. He has to notify R4L of what his changes were and how it broke the ...

steveklabnik · 2025-02-07T20:08:28 1738958908

He does not have to notify them.

> he will still be contacted for information regarding these things.

Just like any other user, and he is free to ignore them just like any other person doing so.

dralley · 2025-02-07T20:08:13 1738958893

How is that different from any C driver currently in existence? Notifying API consumers of what is changing and how and answering the occasional is absolute table stakes for any software developer and throwing a tantrum about that is incredibly juvenile.

FridgeSeal · 2025-02-07T21:19:39 1738963179

How is that literally any different from C code?

There’s 2 kinds of scenarios here:

- Rust code involved: C code change breaks Rust. ~Send~ ~an~ ~email~ ~and~ move on.

- C code involved: inform other C devs, either work with them or wait for them to fix.

The way I see it, either way, the “Rust stuff adds unacceptable amounts of workload” doesn’t really check out.

Edit: turns out he doesn’t even need to inform the Rust devs.