Serialisation of virtual threads

[Dimos Raptis]

Hello everyone,

I remember the initial Loom proposal mentioned serialization of fibers and I can also see that being mentioned under the "Missing Features" section of the home page.
After reading the "State of Loom" post, I noticed that fibers are being replaced by "virtual" threads and will comply with most of the existing APIs. It also seems scheduling/suspension points are not explicit anymore and they become to some extent an implementation aspect of the feature, not necessarily visible to the user.

I was wondering if that has any implications on the ability/desire to implement serialization of them? Could you share any plans on this area?

We are making use of Quasar fibers at the moment and we would like to migrate to the native API. But, in order to do this we would need the ability to suspend-serialize and deserialize-schedule these virtual threads at specific points.

Thanks and apologies if this has been answered already,
Dimos