Displaying 2 results from an estimated 2 matches for "_sr".
Did you mean:
_r
2016 Nov 28
3
RFC: Constructing StringRefs at compile time
...ave to write
"foo"_string_ref_literal, and then provide a macro like `#define LITERAL(x)
x_string_ref_literal`, so that the user writes `StringRef s[] = {
LITERAL("a"), LITERAL("b") }; I'm not sure if that's better or worse than
`StringRef s[] = { "a"_sr, "b"_sr };`, but at least it's greppable this way.
2) Don't allow global tables of StringRefs.
On Mon, Nov 28, 2016 at 11:30 AM Mehdi Amini via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Nov 28, 2016, at 11:27 AM, David Blaikie <dblaikie at gmail.com> w...
2016 Nov 28
3
RFC: Constructing StringRefs at compile time
On Mon, Nov 28, 2016 at 11:01 AM Mehdi Amini <mehdi.amini at apple.com> wrote:
> On Nov 28, 2016, at 9:47 AM, David Blaikie via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> OK - good to know. (not sure we're talking about pessimizing it - just not
> adding a new/possible optimization, to be clear)
>
>
> This does not seem that clear to me. The