You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LLVM.jl currently defines and exports many getter methods with lots of simple functionality:
export DILocation, line, column, scope, inlined_at
""" DILocationA location in the source code."""@checkedstruct DILocation <:MDNode
ref::API.LLVMMetadataRefendregister(DILocation, API.LLVMDILocationMetadataKind)
""" line(location::DILocation)Get the line number of the given location."""line(location::DILocation) =Int(API.LLVMDILocationGetLine(location))
""" column(location::DILocation)Get the column number of the given location."""column(location::DILocation) =Int(API.LLVMDILocationGetColumn(location))
""" scope(location::DILocation)Get the scope of the given location."""functionscope(location::DILocation)
ref = API.LLVMDILocationGetScope(location)
ref ==C_NULL?nothing:Metadata(ref)::DIScopeend""" inlined_at(location::DILocation)Get the location where the given location was inlined."""functioninlined_at(location::DILocation)
ref = API.LLVMDILocationGetInlinedAt(location)
ref ==C_NULL?nothing:Metadata(ref)::DILocationend
This is pretty polluting from a namespace perspective. I wonder if we should move some of these into getproperty/setproperty! methods?
The text was updated successfully, but these errors were encountered:
LLVM.jl currently defines and exports many getter methods with lots of simple functionality:
This is pretty polluting from a namespace perspective. I wonder if we should move some of these into
getproperty
/setproperty!
methods?The text was updated successfully, but these errors were encountered: