Populate Object / Clone Object about fullserializer HOT 5 CLOSED

I'll leave this issue open until populating an object instance works properly.

Clone object is easy to write by just serializing and then deserializing the object, for example:

public static class StringSerializationAPI {
    private static fsSerializer _serializer = new fsSerializer();

    public static T Clone<T>(T value) {
        // step 1: serialize the data
        fsData data;
        var fail = _serializer.TrySerialize(typeof(T), value, out data);
        if (fail.Failed) throw new Exception(fail.FailureReason);

        // step 2: deserialize the data
        object deserialized = null;
        fail = _serializer.TryDeserialize(data, typeof(T), ref deserialized);
        if (fail.Failed) throw new Exception(fail.FailureReason);

        return (T)deserialized;
    }
}

Due the API design of the FS, this clone implementation completely skips any JSON printing/parsing overhead :).

from fullserializer.

Yeah, that is nice. When populate works right, I might end up using your solution for Foundation. I am currently working on the new core.... as I wait for the new uGUI.

from fullserializer.

Oh, nifty. The populate fix should take only one or two lines, though it may be a couple of days before I'm able to get to it.

If you end up using FS and you publish the project to the asset store, I only ask that you rename the FullSerializer namespace to something like Foundation.FullSerializer (to avoid conflicts) if you're not exposing it to the user.

from fullserializer.

+1

from fullserializer.

When deserializing, FS will use the existing object instance when possible (but if you give it an wrong instance type, it'll ignore the existing instance).

from fullserializer.