search for: semadecl

Eli Friedman wrote: > Please file bug reports at llvm.org/bugs/ Filed bugs for all three. I was hoping to fix these now, with some help.

...ecurse2be/build/./tools/clang/lib/AST/Release+Asserts/MicrosoftCXXABI.o differ: byte 7864, line 14 ./tools/clang/lib/Sema/Release+Asserts/AttributeList.o ../../recurse2be/build/./tools/clang/lib/Sema/Release+Asserts/AttributeList.o differ: byte 94793, line 191 ./tools/clang/lib/Sema/Release+Asserts/SemaDecl.o ../../recurse2be/build/./tools/clang/lib/Sema/Release+Asserts/SemaDecl.o differ: byte 538096, line 952 ./tools/clang/lib/Sema/Release+Asserts/SemaDeclAttr.o ../../recurse2be/build/./tools/clang/lib/Sema/Release+Asserts/SemaDeclAttr.o differ: byte 239545, line 405 ./tools/clang/lib/Sema/Release+As...

I'm not advocating AAA. However this is a proposal for more modern thinking regarding the permissiveness of auto in LLVM codebases. Currently the rule on the use of auto is here: https://llvm.org/docs/CodingStandards.html#use-auto-type-deduction-to-make-code-more-readable It is quite strict. It allows the use of auto for * lambdas * iterators because they are long to type * casts to