Swift in Jupyter

[anutosh491 (Anutosh Bhat)]

Hi,

This is Anutosh here (a Project Jupyter and an llvm/clang member) but more importantly a swift newbie

At Project Jupyter, we are trying to bring all languages to the browser using JupyterLite & Web Assembly in the form of a REPL.

The latest one being C++ , one can now do C++

1. Completely in the browser, no local setup required whatsoever
2. Interactively in the form of a REPL

Feel free to try out the C++ kernels on this link JupyterLite

You shall also find a few demo notebooks starting with cppxx.ipynb for demonstrating the use case

Feel free to explore anything from BLAS & LAPACK routines through Openblas & Xtensor, to interactive Jupyter widgets to Graphics using SDL.

3. You can also fetch any 3rd party lib/package as and when you want to use it (and its all gone as soon as you close the instance) . For eg

I plan to ideate more on having a similar kernel for swift just like we did for C++. I say this cause I see quite some similarities

A) For C++, we used clang-repl (based on clang & LLVM's ORC JIT and for this we compiled clang & lld using emscripten)

I see swift offers a repl too built on top of lldb (although architecturally different from clang-repl , I would like to ideate a bit on this)

I would like to discuss more here but being new to swift I have quite some doubts. I tried looking on swift's github trying to locate people/teams responsible for maintaining the swift REPL but wasn't successful.

As a first step could someone point me to the maintainers for this project so that I can put forward my doubts ?

[compnerd (Saleem Abdulrasool)]

This has been done before (incidentally, I was involved in 2 such attempts in the past). The first one was based on using LLDB directly via swift-jupyter as part of Google's Swift4TensorFlow project. The second attempt was based around the new VSCode notebook model.

The LLDB project itself is maintained as part of llvm.org; we do have a fork of it primarily maintained by folks who are already part of the LLDB community.

[compnerd (Saleem Abdulrasool)]

If you want to pick up the work that I had started for the VSCode based approach: VSCode jupyter notebook based REPL is the post and it links to the original PR.

[anutosh491 (Anutosh Bhat)]

Hi,

Thanks for the reply.

I see the Swift Repl is probably a wrapper over LLDB (and this LLDB is maintained as a fork from llvm)

So my next questions is

1. Is it documented somewhere as to what efforts were taken by people working on the REPL to have this separate fork on lldb under swift ? After making the required changes on top of lldb what effort was taken to write the swift repl ? Would it make sense to push this work upstream ?

2. What's the library proving C/C++ API to interact with the swift REPL ? It is swiftImmediate by any chance ? (swift/lib/Immediate at main · swiftlang/swift · GitHub)

Asking this cause as I said for the C++ kernel (GitHub - compiler-research/xeus-cpp: Jupyter kernel for the C++ programming language) whose link I attached above, we used libclangInterpreter from llvm (llvm-project/clang/lib/Interpreter/CMakeLists.txt at main · llvm/llvm-project · GitHub) that exposes the API to interact with clang-repl.

Regards,
Anutosh Bhat

[compnerd (Saleem Abdulrasool)]

@anutosh491

Is it documented somewhere as to what efforts were taken by people working on the REPL to have this separate fork on lldb under swift ? After making the required changes on top of lldb what effort was taken to write the swift repl ?

I'm not sure what the question here actually is intending to ask. LLDB requires forking because of the additional language mode. That language mode requires having the Swift compiler, which is not upstream. While it would be ideal to have the language support in upstream LLDB, that is a massive undertaking.

@anutosh491

Would it make sense to push this work upstream ?

What work are you referring to? The basis for the REPL has been upstreamed, and others in the community have used that to build additional REPLs, such as the one that mojo has.

@anutosh491

What's the library proving C/C++ API to interact with the swift REPL ?

Again, this is very unclear. Who is the actor interacting with the REPL. If you look at the code in the pull request I posted above, there is no library in the middle - it is simply communicating over stdin/stdout.

If this is in context of implementing a jupyter notebook, I would recommend against that. My experiences with writing a jupyter notebook kernel with the C++ APIs was that it is far too fragile. That is why the VSCode notebook approach dooes the direct communication.