Importing needs more details in README and a suggestion about import syntax

[molaeiali]

Issue
You talked about importing in README and in examples "you could instead import the test_import file" but there are no examples of importing anything, I searched project files and found it the syntax is like:

import somefile

and somefile should be in your project dir or in RUMI_PATH dir. Plus, there is no info about where you can import and what happens when you import, Is it like copy and paste the code where you imported it? and you can import code in the middle of the code or at the end? or it should always be first in your file? Does it require once? or if I import something twice, it brings it twice? etc.

Suggestion:
Also, import syntax is not consistent with language syntax I think, It does not require ; at the end of it, and does not have <> " or any similar thing we use in other projects, I think it would be nice to have at least a semi-colon required at the end of the import statement to be consistent.
(I know for example C style includes are not semi-colon required too, but they are in a specific shape or "somefile" that make me think about them as special statements, but here my feeling is import is a statement [Maybe because I'm coming from a JS/TS/Java background])

[MCSH]

Your point about documentation is absolutely valid!

However, about semicolons at the end of import statements, I think it is consistent, given that top-level statements don't include semicolons (with the exception of function declaration). However, I've added a null parser for semicolons in top statements, so if a user, out of habit, write import something; it is still going to compile.

Also, I kind of want o have an import top-level statement with strings as well, but only in cases where we have an absolute path or a relative path in another directory, e.x.,

import "../otherFolder/file.rum"
import "/opt/rumi_lib/something/file2.rum"

But that doesn't mean we should remove the base import statements.

Still, I'm going to keep this issue open, if other people think a semicolon would be necessary, we can change it before a beta release.