Displaying 6 results from an estimated 6 matches for "derivedt".
Did you mean:
derived
2018 Dec 04
4
[cfe-dev] RFC: Modernizing our use of auto
...ting out the type
name. I think people are too eager to use `auto` because it is easy to
write but it makes the types substantially harder for the reader to
understand.
> In the case that came up in review for me, the code I submitted is
> >
> > template <typename BaseT, typename DerivedT>
> > void registerIfNodeMatcher(...) {
> > auto NodeKind = ASTNodeKind::getFromNodeKind<DerivedT>();
> > if (!NodeKind.isNone())
> > NodeCtors[NodeKind] = std::make_pair(MatcherName, Descriptor);
> > }
> >
> > but it was rejected as unreadable...
2013 Nov 04
2
[LLVMdev] compile error when using overloaded = operator of DenseMap
...; /* confluence operation */
};
}
with the following function definition:
void DataFlowValue::set(DMTy emap) {
ExprMap = *emap; //Line153:
}
When I compile, I get the following error:
/home/zeus/masterLLVM/llvm/include/llvm/ADT/DenseMap.h: In member function
‘void llvm::DenseMapBase<DerivedT, KeyT, ValueT, KeyInfoT>::destroyAll()
[with DerivedT = llvm::DenseMap<{anonymous}::Expression, unsigned int>,
KeyT = {anonymous}::Expression, ValueT = unsigned int, KeyInfoT =
llvm::DenseMapInfo<{anonymous}::Expression>]’:
/home/zeus/masterLLVM/llvm/include/llvm/ADT/DenseMap.h:600:5...
2020 Jan 24
3
Module::createRNG() and new PassManager
Correct me if I'm wrong, but is Module::CreateRNG(Pass *) unusable with
the new PassManager? Since each pass is defined as a
llvm::PassInfoMixIn<DerivedT> instead of inheriting from llvm::Pass, it
doesn't seem possible to obtain the underlying llvm::Pass * from e.g.
llvm::ModuleAnalysisManager. Would it make sense to change the
definition/implementation to Module::CreateRNG(StringRef PassName)?
Please CC me on responses.
Thanks,
Dominic
2018 Nov 25
6
RFC: Modernizing our use of auto
...nswer in the coding guidelines to
whether
void foo()
{
if (auto ParserInstance = Parser::getFromArgs(Args); ParserInstance)
obj.someApi(ParserInstance);
}
is ok or not.
In the case that came up in review for me, the code I submitted is
template <typename BaseT, typename DerivedT>
void registerIfNodeMatcher(...) {
auto NodeKind = ASTNodeKind::getFromNodeKind<DerivedT>();
if (!NodeKind.isNone())
NodeCtors[NodeKind] = std::make_pair(MatcherName, Descriptor);
}
but it was rejected as unreadable and I was given a link to the coding
guidelines.
'NodeKi...
2013 Nov 04
0
[LLVMdev] compile error when using overloaded = operator of DenseMap
...h the following function definition:
>
> void DataFlowValue::set(DMTy emap) {
> ExprMap = *emap; //Line153:
> }
>
> When I compile, I get the following error:
>
> /home/zeus/masterLLVM/llvm/include/llvm/ADT/DenseMap.h: In member function
> ‘void llvm::DenseMapBase<DerivedT, KeyT, ValueT, KeyInfoT>::destroyAll()
> [with DerivedT = llvm::DenseMap<{anonymous}::Expression, unsigned int>, KeyT
> = {anonymous}::Expression, ValueT = unsigned int, KeyInfoT =
> llvm::DenseMapInfo<{anonymous}::Expression>]’:
> /home/zeus/masterLLVM/llvm/include/llvm/...
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,