fallback system about constructive HOT 4 CLOSED

We might trigger the fallback if we encounter a corrupted object too. for instance a function with class "data.frame" would at the moment be reconstructed with construct_idiomatic.data.frame() and this will fail.

If we have a is_corrupted_*() function family, every method can start with if(is_corrupted_*(x)) NextMethod(). We can also make these checks optional.

from constructive.

After #65 it might be as simple as :

if (constructor == "next") NextMethod()

from constructive.

I think all objects of class list should have a list() constructor, that's we'll fall back to it if the object is corrupted and a list.

More generally :

• we check if an object is corrupted
• if it is we fall back on another constructor, by default an atomic constructor (simplest constructor for the atomic type, with adequate attribute reparation)
• list() will be used for data frames etc, c() for atomic vectors, function for functions etc

In the example of a function with a data frame class, we will find that the data frame is corrupted, and fall back to the function constructor.

Right now we cannot do this because we run construct_idiomatic then repair_attributes, so we'd run the wrong repair_attributes.

To be done after we unite onstruct_idiomatic and repair_attributes

from constructive.

done with #172

from constructive.