Displaying 6 results from an estimated 6 matches for "134921".
2020 Feb 18
2
amount of camelCase refactoring causing some downstream overhead
...ing causing some downstream overhead
My understanding is that LLVM's general policy is to not let
downstream slow down upstream development. The C++ API explicitly
unstable.
Note that we are even considering renaming variables globally:
https://lists.llvm.org/pipermail/llvm-dev/2019-September/134921.html
Michael
Am Mo., 17. Feb. 2020 um 06:04 Uhr schrieb Ties Stuij via llvm-dev
<llvm-dev at lists.llvm.org>:
>
> Hi there,
>
> At the end of last week we saw a number of commits go in that were camelCasing batches of MCStreamer::Emit* and AsmPrinter::Emit* functions.
>
>...
2020 Feb 18
2
amount of camelCase refactoring causing some downstream overhead
...nding is that LLVM's general policy is to not let
> > downstream slow down upstream development. The C++ API explicitly
> > unstable.
> >
> > Note that we are even considering renaming variables globally:
> > https://lists.llvm.org/pipermail/llvm-dev/2019-September/134921.html
> >
> > Michael
> >
> > Am Mo., 17. Feb. 2020 um 06:04 Uhr schrieb Ties Stuij via llvm-dev
> > <llvm-dev at lists.llvm.org>:
> >> Hi there,
> >>
> >> At the end of last week we saw a number of commits go in that were
> camelCasi...
2020 Feb 17
4
amount of camelCase refactoring causing some downstream overhead
Hi there,
At the end of last week we saw a number of commits go in that were camelCasing batches of MCStreamer::Emit* and AsmPrinter::Emit* functions.
For example:
- https://reviews.llvm.org/rG549b436beb4129854e729a3e1398f03429149691
- https://reviews.llvm.org/rGa55daa146166353236aa528546397226bee9363b
- https://reviews.llvm.org/rG0bc77a0f0d1606520c7ad0ea72c434661786a956
Unfortunately all these
2020 Feb 19
7
amount of camelCase refactoring causing some downstream overhead
...39;s general policy is to not let
>> > downstream slow down upstream development. The C++ API explicitly
>> > unstable.
>> >
>> > Note that we are even considering renaming variables globally:
>> > https://lists.llvm.org/pipermail/llvm-dev/2019-September/134921.html
>> >
>> > Michael
>> >
>> > Am Mo., 17. Feb. 2020 um 06:04 Uhr schrieb Ties Stuij via llvm-dev
>> > <llvm-dev at lists.llvm.org>:
>> >> Hi there,
>> >>
>> >> At the end of last week we saw a number of commit...
2020 Feb 20
3
amount of camelCase refactoring causing some downstream overhead
...ead
>
> My understanding is that LLVM's general policy is to not let
> downstream slow down upstream development. The C++ API explicitly
> unstable.
>
> Note that we are even considering renaming variables globally:
> https://lists.llvm.org/pipermail/llvm-dev/2019-September/134921.html
>
> Michael
>
> Am Mo., 17. Feb. 2020 um 06:04 Uhr schrieb Ties Stuij via llvm-dev
> <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>:
>> Hi there,
>>
>> At the end of last week we saw a number of commits go in that were camelCasing b...
2020 Feb 19
5
amount of camelCase refactoring causing some downstream overhead
...ead
>
> My understanding is that LLVM's general policy is to not let
> downstream slow down upstream development. The C++ API explicitly
> unstable.
>
> Note that we are even considering renaming variables globally:
> https://lists.llvm.org/pipermail/llvm-dev/2019-September/134921.html
>
> Michael
>
> Am Mo., 17. Feb. 2020 um 06:04 Uhr schrieb Ties Stuij via llvm-dev
> <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>:
>> Hi there,
>>
>> At the end of last week we saw a number of commits go in that were camelCasing b...