Jacob Lifshay

> Unfortunately that doesn't help. For example, it needs libsrist-dev, libjxl-dev and librav1e-dev none of which are in jammy. I've tried backporting libjxl-dev, but it needed 4 other other packages...

> if it isn't in jammy's ffmpeg why go to a lot of effort to enable all the new codecs and stuff in a backport to jammy? imo just disable...

> > if it isn't in jammy's ffmpeg why go to a lot of effort to enable all the new codecs and stuff in a backport to jammy? imo just...

> > So as long as it is communicated well that this is known to be broken in some scenarios, I am ok with that > > ok, in that...

this would be quite useful for stabilizing `std::error::Error::type_id`, which currently has several workarounds to prevent it from being overridden: https://doc.rust-lang.org/1.80.1/src/core/error.rs.html#88-100 cc rust-lang/rust#60784

> Associated constants could also be made final as a further possibility. imo `final` should be supported on any item you can put in a trait definition: associated types associated...

I'd like to bring back the install button directly on the list of mods, that way if you're using a new luanti install and are going through the list to...

one problem I noticed with the Storage API -- afaict it doesn't support read-only graphs! -- it has functions for adding/removing/modifying nodes even though not all graph types support that......

i'll mention that not all graphs have sequential `usize` node/edge indexes (e.g. in my example a few comments above, edges are never assigned indexes, and nodes have one of two...

> By your argument, #[no_mangle] alone should already be unsafe since linking with outside code is unsafe. `#[no_mangle]` is unsafe: https://doc.rust-lang.org/edition-guide/rust-2024/unsafe-attributes.html