This request was made by a user who wrote to me that there is no real means of debugging/investigating a wrong cell.
Some cells would give a symbol not found/failed to materialize symbols error through the orc jit/ clang-repl's wasm backend which makes it clear as to where the error is but if the error is on the frontend clang size there is no real means of figuring out what went wrong.
This is also inspired by other kernels like let's say fortran kernel through loftran
https://github.com/lfortran/lfortran/blob/43e8134c455940a75b92f35b262020d7fe29daa9/doc/src/ast_and_asr.ipynb
This request was made by a user who wrote to me that there is no real means of debugging/investigating a wrong cell.
Some cells would give a
symbol not found/failed to materialize symbolserror through the orc jit/ clang-repl's wasm backend which makes it clear as to where the error is but if the error is on the frontend clang size there is no real means of figuring out what went wrong.This is also inspired by other kernels like let's say fortran kernel through loftran
https://github.com/lfortran/lfortran/blob/43e8134c455940a75b92f35b262020d7fe29daa9/doc/src/ast_and_asr.ipynb