Rename LFortran namespace to LCompilers

[Thirumalai-Shaktivel]

Closes: #403
Related: #560

[certik]

Let's first sync libasr with LFortran / LPython, then do this change in both projects at once, otherwise it will be quite hard to sync.

[Thirumalai-Shaktivel]

$ ctest 
Test project /home/thirumalai/Open_Source/lpython
    Start 1: test_stacktrace
1/2 Test #1: test_stacktrace ..................   Passed    0.92 sec
    Start 2: test_lpython
2/2 Test #2: test_lpython .....................***Failed    0.15 sec

50% tests passed, 1 tests failed out of 2

Total Test time (real) =   1.08 sec

The following tests FAILED:
          2 - test_lpython (Failed)
Errors while running CTest
Output from these tests are in: /home/thirumalai/Open_Source/lpython/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.

@certik, How to resolve this error?

[certik]

You have to see what the error is by executing ./src/lpython/test_lpython.

[Thirumalai-Shaktivel]

$ ./src/lpython/tests/test_lpython 
[doctest] doctest version is "2.4.8"
[doctest] run with "--help" for options
===============================================================================
/home/thirumalai/Open_Source/lpython/src/lpython/tests/test_error_rendering.cpp:59:
TEST CASE:  Error Render: primary/secondary labels, single line

/home/thirumalai/Open_Source/lpython/src/lpython/tests/test_error_rendering.cpp:94: ERROR: CHECK( out == ref ) is NOT correct!
  values: CHECK( semantic error: Error with label no message
 --> input:1:5
  |
1 | One line text
  |     ^^^^ 
 == semantic error: Error with label no message
 --> input:1:5
  |
1 | One line text
  |     ^^^^
 )

===============================================================================
[doctest] test cases:  37 |  36 passed | 1 failed | 0 skipped
[doctest] assertions: 210 | 209 passed | 1 failed |
[doctest] Status: FAILURE!

Both the strings seems similar!

[certik]

Is there an extra ) at the end?

[Thirumalai-Shaktivel]

I think the extra ) is the closing paren for CHECK (

[certik]

Is this on Windows? I wonder if it is some CR / LF issue.

[Thirumalai-Shaktivel]

Nah. It fails on Linux! Yup, It might be CR / LF issue.

[certik]

It's in the file src/lpython/tests/CMakeLists.txt, you can try to debug it.

However, I would recommend to split this into smaller changes and just get one smaller change at a time. And make sure to submit a PR both to LPython and LFortran, so that we can keep the libasr synchronized.

[Thirumalai-Shaktivel]

If anything else to be modified, do let me know.

[certik]

We need to sync ASR first, otherwise it will be a lot of work I think.

[Thirumalai-Shaktivel]

This PR is ready!
I think the only left-out part in LIBASR is lfortran_intrinsics

[certik]

Yes, we should do it, but we need to do this both in LFortran and LPython at the same time.

[Thirumalai-Shaktivel]

Cool, I will submit a PR with same changes there.

[Thirumalai-Shaktivel]

These changes are made using LLVM 15. But, CI uses LLVM 11. So, the failure.

[Thirumalai-Shaktivel]

@certik, This PR is ready for final review.

[Thirumalai-Shaktivel]

I'm spitting this PR into different PR's.
Starting with LFortran Assert