[cfe-dev] libc++ internals visibility rational
Mehdi Amini via cfe-dev
cfe-dev at lists.llvm.org
Fri Mar 31 22:46:20 PDT 2017
Hi,
I’m wondering about libc++ visibility for the internals of the library. For example why do we define:
_LIBCPP_INLINE_VISIBILITY
void __construct_at_end(size_type __n, const_reference __x);
with inline/hidden visibility, but not this one:
template <class _ForwardIterator>
typename enable_if <__is_forward_iterator<_ForwardIterator>::value, void>::type
__construct_at_end(_ForwardIterator __first, _ForwardIterator __last, size_type __n);
Thanks,
—
Mehdi
More information about the cfe-dev
mailing list