Erroreous `newtruct` member assignment not caught

[dreyer]

A user can assign elments of the wrong type to newstruct member. Singular complains, but does the assignment anyway yielding inconsistent structures:

> newstruct("wrapping","int i");
>
. wrapping wrap;
> intvec v=(1,2,3);
>
. wrap.i = v;
   ? type change in member i (int(439) -> intvec(443))
   ? error occurred in or before STDIN line 6: `wrap.i = v;`
>
. wrap;
i=1,2,3
> wrap.i;
1,2,3
> typeof(wrap.i);  // !!! -> intvec
intvec

If the assignment could not be avoided internally, the newstruct should be reseted afterwards.

I tested this with the release 3-1-4 and the recent development version.

[hannes]

fixed.