a) significant down time b) potential loss/corruption of the existing database
Maybe the benefit of a timely update would outweigh cost of prolonged (e.g. a day) downtime and a database reset, as the instance if currently barely active and amount of accumulated content is currently small.
Obviously, it does not mean further updates should be disruptive.
Playground link is mangled as well: I needed to manually replace &s with & to make it load the gist.
I asked in the Rust Discord channels and it seems like my approach is fine. Even the mutable version is okay and doesn’t need to be unsafe if it returns the reference with self’s lifetime.
Then maybe publish it as a mini-crate (e.g. any-slice), ideally with a link to the discussion that proves that it is sound.
Note: both code fragments and links contain things like & which makes them inoperable as is.
Is anyvec crate of relevance?
Maybe this is the problem? Should there be more than one admin?