bearophile, el 14 de enero a las 19:05 me escribiste: > Andrei Alexandrescu: > > Because @disable applies to any function. > > What's the purpose of disabling any random function? (Is such extra > generality worth its cognitive cost?)
Exactly, it seems to me that the generalization in this case is counterproductive. What's the point on disabling a function, except for those automatically generated by the compiler. I this it would be cleaner to add some kind of annotation @noncopiable to the struct/class, instead of annotating each constructor. -- Leandro Lucarella (AKA luca) http://llucax.com.ar/ ---------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ---------------------------------------------------------------------- Do not get mad with others Because they know more than you It is not their fault
