On Tue, 24 Apr 2018, Michael Matz wrote: > Well, documentation is both: a description and specification. If we > change the documentation now we might not be in the position anymore to > change behaviour and docu back because people might in the meanwhile rely > on the specification. Which is why documentation changes that promise a > certain behaviour are exactly the ones that shouldn't be rushed (even less > than actual implementation changes).
My patch isn't making any promises; in a nutshell, it says "must use constraints", which is the most tight specification and doesn't open any new doors (in contrast with the position that you were arguing, which would be a new promise). Did the other changes in patch 1 look fine to you, content-wise? Thanks. Alexander
