feat: one could add a type member that already exists (equals but not same) and modify it afterwards

[monperrus]

fix #1862

[pvojtechovsky]

throw new SpoonException("ooops, impossible to have two constructors with the same signature");
I would say that is not good idea to fail when Spoon model is not 100% compilable/consistent.

1. we cannot assure that Spoon model is 100% consistent
2. during Spoon model transformation/refactoring the model might be temporarily inconsistent - until refactoring is finished. And your change might cause that refactoring fails in the middle or it would need more complicated algorithm, which avoids inconsistent states.

I would prefer instead a new spoon model method checkConsistency, which would report all inconsistencies. Such check would be then part of this consistency checking.

WDYT?

[monperrus]

Yes, I agree. Here is the alternative solution.