search for: find_if

Displaying 9 results from an estimated 9 matches for "find_if".

2018 Dec 04
4
[cfe-dev] RFC: Modernizing our use of auto
On Wed, Nov 28, 2018 at 6:25 PM Chris Lattner via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Generally no IMO, because the cases that produce optional are not obvious. > Just to say, +1 from me too. > > > * Can we use auto in c++14 lambda arguments with llvm::find_if(C, > [](const auto& i) { ... }) for example? > > * We need to use auto for structured bindings, if those are used. > > These both get into “yes, if the type is contextually obvious”. I’m not > sure how to specify this though. > > Perhaps the rule came be rewritten more...
2018 Nov 25
6
RFC: Modernizing our use of auto
...es, given that LLVM will allow C++17 features in a few months. For example: * Can we use auto in the initializer of range-for statements? * Can we use auto in the initializer of if() statements? * Can we use auto with llvm:Optional instances? * Can we use auto in c++14 lambda arguments with llvm::find_if(C, [](const auto& i) { ... }) for example? * We need to use auto for structured bindings, if those are used. I know some people are very opposed to use of auto except in exceptional circumstances, but * Some features force it a bit * Elsewhere it is becoming more common for it to be reasona...
2016 Nov 20
3
uninitialized values in Attributes.cpp
...ibute (Attributes.cpp:421) ==29299== by 0x13FCF12: hasAttribute (Attributes.cpp:186) ==29299== by 0x13FCF12: operator() (Attributes.cpp:627) ==29299== by 0x13FCF12: operator()<const std::pair<unsigned int, llvm::Attribute> *> (predefined_ops.h:234) ==29299== by 0x13FCF12: __find_if<const std::pair<unsigned int, llvm::Attribute> *, __gnu_cxx::__ops::_Iter_pred<(lambda at ../lib/IR/Attributes.cpp:627:3)> > (stl_algo.h:140) ==29299== by 0x13FCF12: __find_if<const std::pair<unsigned int, llvm::Attribute> *, __gnu_cxx::__ops::_Iter_pred<(lambda...
2016 Nov 20
3
uninitialized values in Attributes.cpp
...= by 0x13FCF12: hasAttribute (Attributes.cpp:186) >> ==29299== by 0x13FCF12: operator() (Attributes.cpp:627) >> ==29299== by 0x13FCF12: operator()<const std::pair<unsigned int, >> llvm::Attribute> *> (predefined_ops.h:234) >> ==29299== by 0x13FCF12: __find_if<const std::pair<unsigned int, >> llvm::Attribute> *, __gnu_cxx::__ops::_Iter_pred<(lambda at >> ../lib/IR/Attributes.cpp:627:3)> > (stl_algo.h:140) >> ==29299== by 0x13FCF12: __find_if<const std::pair<unsigned int, >> llvm::Attribute> *, __gnu_c...
2006 Oct 30
1
QueryParser and prefixes
Hi all, My app uses prefixes for user-defined labels and directory names. Since these are case-sensitive, I chose XLABEL and XDIR respectively. Labels and directories may start with an upper-case, so a ":" is always inserted between the prefix and the term itself. These prefixes are mapped with add_boolean_prefix to "dir" and "label". Let's imagine I index a
2018 Dec 31
4
RFC: Modernizing our use of auto
On Dec 16, 2018, at 11:44 AM, Stephen Kelly via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 25/11/2018 14:43, Stephen Kelly via llvm-dev wrote: >> 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: > > Hi, > > Thanks for the input on this topic,
2017 Jul 17
3
A bug related with undef value when bootstrap MemorySSA.cpp
It seems MemorySSA.cpp is the only real code where we found the problem happening. Is it possible to change the source of MemorySSA.cpp to hide the problem and buy some time for now? Now we use an empty generic_def_path_iterator with Optional<ListIndex> N being initialized by None as the end of range. Can we initialize the Optional var with a special value instead of None?
2006 Apr 05
1
build error : xapian-core-0.9.4_svn6707 with UTF-8 patch
...ichar_isalnum' cannot be used as a function /u1/olly/xapian-svn-snapshot/trunk/xapian/xapian-core/queryparser/queryparser.lemony:194: warning: unused variable 'gchar' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../include/c++/3.4.5/bits/stl_algo.h: In function `_InputIterator std::find_if(_InputIterator, _InputIterator, _Predicate, std::input_iterator_tag) [with _InputIterator = AccentNormalisingItor, _Predicate = bool]': /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../include/c++/3.4.5/bits/stl_algo.h:336: instantiated from `_InputIterator std::find_if(_InputIterator, _I...
2006 Mar 03
1
xapian-0.9.4 queryparser build errors after applying utf-8 patch
...or*' in '*it' /u1/olly/xapian-svn-snapshot/tags/0.9.4/xapian/xapian-core/queryparser/queryparser.lemony:539: error: `g_unichar_isalnum' cannot be used as a function /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_algo.h: In function `_InputIterator std::find_if(_InputIterator, _InputIterator, _Predicate, std::input_iterator_tag) [with _InputIterator = AccentNormalisingItor, _Predicate = bool]': /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_algo.h:336: instantiated from `_InputIterator std::find_if(_InputIterator, _Inp...