Assem Medhat
Assem Medhat
Yeah, that's because of how `print_arr` pass handles array printing when with stringformat. before print refatorings we didn't use stringformat, while now we always use stringformat. and printing arrays with...
It's related to how we rely on null character termination with strings, as a result the return of `str(3:6)` which is a `StringSection` node is a copy of `str` not...
Thanks for working on this. The bug seems simple but yet critical, as it points out to the wrong way LFortran is handling strings. We're currently working on refactoring strings,...
The changes seems right, but I think the problem resides here `lfortran_str_slice(str, left, right, step, left_present, right_present)` as it creates a new copy of the slice, not the actual memory...
Yeah. I think the fix should be there, but we depend on null char with strings with lots of operations, so slicing a string and not returning the slice without...
I can see that this approach could be used to handle formatting appropriately, but It hurts speed very much that even an array with 10000 elements is able to fill...
It also needs to be solved out as it hurts the benchmark we do on the packages, It should speed up the printing and the writing. I'll add a SNAP...
That's exactly what I have been thinking about. This approach would solve multiple opened issues. This issue for example https://github.com/lfortran/lfortran/issues/4400, It creates nested loop for total of 10000 iterations and...
@NishantBansal2003. I think you can push a PR, It'd be more convenient to see where you've made the changes in the codebase.