Generally usable persistent objects

[krakjoe]

As part of #7212 we have to invent the concept of persistent objects.

Here is another possible approach to persistent objects, I'm not sure if it's flexible enough to do enums yet, but it looks technically simpler and more generally usable.

/cc @bwoebi @nikic what do we think of this approach ? and if we like it, what have I missed ?

[krakjoe]

CI is going to fail, because of fixed object ids in a lot of tests ... I'm going to ignore that while we decide if this is any good ...

[kocsismate]

Could we use these persistent objects for backing persistent connections instead of using persistent resources?

[krakjoe]

Could we use these persistent objects for backing persistent connections instead of using persistent resources?

A default persistent connection maybe, because you'd need to know how to construct the object at MINIT stage.

[krakjoe]

Since the main use case was enums, and this doesn't look suitable for that without jumping through many hoops, and since Nikita has a better proposal for that, I'm gonna close this.

I don't think it's a terrible approach, maybe we revisit in the future but for now I'm not going to put more time into it.