Ondřej Čertík

Here is one way to fix this: https://github.com/lfortran/lfortran/pull/8226, just needs to be finished.

This is now fixed, and we test it at the CI, so regressions shouldn't happen in the future.

> **Concerns** > > * [ ] Naming of `print_t` only member to be 'text', is that a good choice? I think so. > > * [ ] Now, with...

The replace symbolic is for symbolic (SymPy like) expressions. The Print replacement allowed printing the expressions. Those should be now handled in StringFormat. @anutosh491 can help with this later. For...

@assem2002 let's finish this, I think it is almost done.

Thank you. I think this is great! Can you please resolve the conflicts? To summarize, this PR makes the `Print` node accept just the text as a required argument. Much...

We need to print the empty space for `lfortran --print-leading-space examples/expr2.f90` (one way or the other), then we can merge.

I'll open this issue until the things Pranav said are done, then we can close it.

Let me see if I can explain it better. We should assume that `fpm` is smart enough to completely build the project on its own. We are very close and...

Yes exactly. And not just be done with it, but you can keep using `fpm` to keep the other build systems up-to-date. When you have a bigger project, the inter-dependencies...