Displaying 4 results from an estimated 4 matches for "ownsdeserializationlisten".
Did you mean:
ownsdeserializationlistener
2014 Nov 13
2
[LLVMdev] New type of smart pointer for LLVM
...cases of
> conditional ownership (I'm sure there are others that don't fit the exact
> naming convention I grep'd for):
>
> In Clang, simply grepping for "Owns" comes up with the following boolean
> members:
>
> CodeGenAction::OwnsVMContext
> ASTReader::OwnsDeserializationListener
> Diagnostic::OwnsDiagClient
> Preprocessor::OwnsHeaderSearch
> TokenLexer::OwnsTokens
> Action::OwnsInputs (this ones trickier - it's a boolean that indicates
> whether all the elements of a vector<T*> are owned or unowned)
> ASTUnit::OwnsRemappedFileBuffers
> Veri...
2014 Oct 08
2
[LLVMdev] New type of smart pointer for LLVM
[+cfe-dev]
This conversation has already been happening on llvm-dev so there's no good
way for me to capture the entire existing discussion (so I'm jumping you in
part-way) & the subject line could be more descriptive, but I wanted to add
Clang developers since many of the interesting cases of conditional
ownership I've seen were in Clang.
I know some of you are also on llvm-dev
2014 Nov 13
2
[LLVMdev] [cfe-dev] New type of smart pointer for LLVM
...nership (I'm sure there are others that don't fit the exact
>> naming convention I grep'd for):
>>
>> In Clang, simply grepping for "Owns" comes up with the following boolean
>> members:
>>
>> CodeGenAction::OwnsVMContext
>> ASTReader::OwnsDeserializationListener
>> Diagnostic::OwnsDiagClient
>> Preprocessor::OwnsHeaderSearch
>> TokenLexer::OwnsTokens
>> Action::OwnsInputs (this ones trickier - it's a boolean that indicates
>> whether all the elements of a vector<T*> are owned or unowned)
>> ASTUnit::OwnsRemap...
2014 Oct 01
4
[LLVMdev] New type of smart pointer for LLVM
On Wed, Oct 1, 2014 at 3:14 PM, Anton Yartsev <anton.yartsev at gmail.com>
wrote:
> Ping!
>
> Suggested is a wrapper over a raw pointer that is intended for freeing
> wrapped memory at the end of wrappers lifetime if ownership of a raw
> pointer was not taken away during the lifetime of the wrapper.
> The main difference from unique_ptr is an ability to access the wrapped