The REPL makes a swift compiler, in which it runs your code (obvious...) So
when you do "import " in the REPL, we need to load that module
into our swift compiler. In the lldb REPL that is managed in
SwiftExpressionParser::PerformAutoImport. This will call lldb's
SwiftASTContext::FindAndLoadM
> On Aug 19, 2016, at 2:26 PM, Daniel Dunbar via swift-lldb-dev
> wrote:
>
>
>> On Aug 19, 2016, at 2:22 PM, Todd Fiala wrote:
>>
>> First off, I think the whole LLDB team can agree on the simple principle
>> that tests that sometimes fail is not something we’re shooting for, so we’re
>> o
I have no formal objections to switching lldb to C++14. I haven't been
following what is in C++14, but presumably it's purely additive? If so then
except for bugs this should be a no-op.
My only reservation is it seems a little odd to adopt a "use C++14" policy for
Swift lldb and not for ll
Next time round should succeed, I forgot to git push the commit that fixed the
bug these tests were failing on...
Jim
> On Jan 16, 2018, at 4:24 PM, swift...@swift.org wrote:
>
> [FAILURE] oss-lldb-swift-4.1-incremental-osx [#285]
>
> Build URL:https://ci.swift.org/job/oss-lldb-swift-4.1-
