The REPL prompt, initially defined like so λ >, is none the less fed the newly added path name despite the loading failed.
That seems to me like unintended behaviour because of the visual noise and a possible misinterpretation leading to the belief that some symbols are actually imported in the current environment.
Run the Steel REPL:
steel
Load a wrongly named or inexistant file/path name:
:load utilities.scm
An non-blocking error occurs:
No such file or directory (os error 2)
The prompt is however fed with a non-loaded path name:
λ > (utilities.scm) >
Here is the actual result on my machine:
EDIT:
The same issue occurs when the file tentatively loaded actually exists.
Despite failing to load that said file due to a whatever compiling error, the prompt is still fed the path name, which again is an undesirable consequence.
:load <existing_file.scm> produces the following result:
λ > :load let02.scm
error[E09]: Parse
┌─ let02.scm:15:2
│
15 │ (let ([x 3]
│ ^^^ Parse: Syntax Error: let expects an expression, found none
λ (let02.scm) >
On a side note:
It could possibly be tagged as a "good first issue".
It could be subject to a specific colored nomenclatur, alongside Mismatch brackets (e.g. could be called with bright().cyan()) to determine a "notice" kind of messages to convey feed-back regarding to criticality to the user.
Could be extended to the point where we would land a full nomenclatur:
notice < warning < error < fatal error.
Issue encountered using Steel v 0.5.0 1fb88e5
The REPL prompt, initially defined like so
λ >, is none the less fed the newly added path name despite the loading failed. That seems to me like unintended behaviour because of the visual noise and a possible misinterpretation leading to the belief that some symbols are actually imported in the current environment.Run the Steel REPL:
steelLoad a wrongly named or inexistant file/path name:
:load utilities.scmAn non-blocking error occurs:
No such file or directory (os error 2)The prompt is however fed with a non-loaded path name:
λ > (utilities.scm) >Here is the actual result on my machine:
EDIT: The same issue occurs when the file tentatively loaded actually exists. Despite failing to load that said file due to a whatever compiling error, the prompt is still fed the path name, which again is an undesirable consequence.
:load <existing_file.scm>produces the following result:On a side note:
Mismatch brackets(e.g. could be called withbright().cyan()) to determine a "notice" kind of messages to convey feed-back regarding to criticality to the user.Could be extended to the point where we would land a full nomenclatur: notice < warning < error < fatal error.