On 8/20/2011 4:24 PM, Jacob Carlborg wrote:
2. What are the prospects for submitting this for inclusion in Phobos?
Serialization is something basic and universally needed enough that it
should not require a third-party library.
From my part:
* Remove all Tango/D1 specific code
* Add documentation
* There are some few things left in the rewrite process
Ok, it sounds like this isn't going to be ready that soon. I'll start
using it as-is, as a third party library. Then I can make suggestions,
file bug reports, etc. and streamline its eventual Phobos review.
* I've made some modifications to the XML module in Phobos, these need
to be applied as well
If we're really lucky, by the time your turn in the review queue comes
along, Phobos will have a new and much better XML module, since Thomas
Sowinki is apparently working on one.
* Probably something else I can't think of right now
I'm not particular happy about removing the Tango/D1 specific code if
I'm not sure that the library can be included in Phobos.
Hmm. We could review the module before you remove it, with the
assumption that this code will be removed if accepted.
Currently you could serialize the data an pass it send it over to
another thread and deserialize on the other side, but I'm guessing this
would be not very effective. I'm not exactly sure what's needed to be
done to make a clone archive and what can be shared but as you say, the
necessary introspection already work.
Right. The idea would be to bypass serializing and unserializing and
leverage the introspection that Orange provides to create an efficient
clone() function. This is mostly a long-term prospect, to be considered
more seriously if/when Orange gets into Phobos. All we'd need from
orange is an archiver that efficiently clones without actually
serializing or deserializing anything. Given this, the changes to
std.concurrency would be trivial.
