[llvm-dev] LLVM deprecation policy
Paul C. Anagnostopoulos via llvm-dev
llvm-dev at lists.llvm.org
Fri Aug 7 11:12:31 PDT 2020
Oh my. You think I should patch every .td file in the system? That sounds a bit scary. I wrote a new test for range lists that tests the old and new range punctuator. And a release note is certainly in order. But I wasn't planning to patch all 600 .td files.
At 8/7/2020 01:56 PM, David Blaikie wrote:
>Fine by me to say the old thing's deprecated.
>
>Ideally, if it's not too painful - would be good if you could do a
>complete migration to the new thing & remove the old thing, to help
>keep things streamlined. (over multiple patches, with some
>notification to llvm-dev and in release notes about the old thing
>being deprecated and encouraging folks to move to the new thing ahead
>of the removal of the old thing)
>
>On Fri, Aug 7, 2020 at 9:47 AM Paul C. Anagnostopoulos via llvm-dev
><llvm-dev at lists.llvm.org> wrote:
>>
>> I checked the Developer Policy and Coding Standards but couldn't find anything about deprecation. If I were to replace a simple bit of syntax in TableGen, what would I say in the documentation? Was the old syntax "deprecated"; or the new syntax "preferred"; or the old syntax simply not documented?
More information about the llvm-dev
mailing list