Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Todd Fiala via lldb-commits
Great. Back soon... On Wed, Nov 16, 2016 at 3:50 PM, Zachary Turner wrote: > No you can go ahead. The new changes I found are not specific to Mac, I > should find problems if there's any with the additional changes. > > On Wed, Nov 16, 2016 at 3:42 PM Todd Fiala wrote: > >> Okay cool. I'm bu

Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Zachary Turner via lldb-commits
No you can go ahead. The new changes I found are not specific to Mac, I should find problems if there's any with the additional changes. On Wed, Nov 16, 2016 at 3:42 PM Todd Fiala wrote: > Okay cool. I'm building against this now. Should I hold off testing? > > On Wed, Nov 16, 2016 at 3:41 PM

Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Todd Fiala via lldb-commits
Okay cool. I'm building against this now. Should I hold off testing? On Wed, Nov 16, 2016 at 3:41 PM, Zachary Turner wrote: > It's no problem, I actually found a few functions I forgot to convert, so > I'm making some additional changes. Nothing that requires additional > testing, but at the

Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Zachary Turner via lldb-commits
It's no problem, I actually found a few functions I forgot to convert, so I'm making some additional changes. Nothing that requires additional testing, but at the very least I won't be able to get this in until tomorrow at the earliest, so it's no biggie. On Wed, Nov 16, 2016 at 3:17 PM Todd Fial

Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Todd Fiala via lldb-commits
Hey Zachary, I had to run home unexpectedly. The build worked but I left before the test results came out. If you ran it on Linux and the Linux tests passed, we can address issues that show up on the macOS side. I will also try it at home on macOS, but I don't think you need to hold up with the

Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Zachary Turner via lldb-commits
Hey Todd, Did you run the tests earlier? If so what was the result? No worries if you didn't run them yet, but it sounded like you were already kicking it off at 11:30. Just want to make sure you didn't finish and forget to update with the result :) On Wed, Nov 16, 2016 at 12:38 PM Todd Fiala

Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Todd Fiala via lldb-commits
Yep - I followed that. I'm just doing the "build + test" verification on macOS. On Wed, Nov 16, 2016 at 11:41 AM, Zachary Turner wrote: > BTW, I would still like to get Chris to take a look at my usage of > llvm::Twine. Even if it works, I'm not sure if I used it correctly. > > On Wed, Nov 16

Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Zachary Turner via lldb-commits
BTW, I would still like to get Chris to take a look at my usage of llvm::Twine. Even if it works, I'm not sure if I used it correctly. On Wed, Nov 16, 2016 at 11:36 AM Zachary Turner wrote: > Either way is fine, I think you might have hit a merge conflict if you > stacked them, but if you've al

Re: [Lldb-commits] [PATCH] D26721: Make AutoComplete code use StringRef

2016-11-16 Thread Zachary Turner via lldb-commits
Either way is fine, I think you might have hit a merge conflict if you stacked them, but if you've already worked through it, then no big deal. On Wed, Nov 16, 2016 at 11:30 AM Todd Fiala wrote: > tfiala added a comment. > > I'm going to test this one now, stacked on top of the final macOS-worki