Open bjornregnell opened 1 year ago
Also when detecting --help
among options it should not start to assume its a library...
Thanks for reporting! As mentioned on discord, this is done on purpose to make people acknowledge they are not using a pinned toolkit version.
I wonder if instead we should have a warning when latest is used implicitely. Better for the users. The minimum we should do is do a better error message.
Yes, well, I think it is better to allow start of the REPL, e.g. after acknowledging the toolkit version used, as a warning/message in terminal. I mean starting the repl is for experimentation and you don't know the version by hart. "Latest" is also cryptic and verbose to a beginner.
It would also be cool if there was a setting to make a "naked" start of the repl (by scala-cli
or later scala
or scala-cli repl
) would include the latest toolkit on classpath by default. This way the user can opt in for this more dynamic, beginnerfriendly "stdlib"... (compare how --power can be set to on by default and how that is suggested at its first use and automatically set to on after a question... Y/n)
Version(s) 1.0.1
Describe the bug Misleading error messages when issuing
scala-cli --toolkit
lead to this failed session:Expected behaviour When an argument is missing the error message should show what argument can be used.
But in this case the whole UX failure could be prevented by just staring the repl with the latest toolkit on classpath.
Assuming
latest
by default seems reasonable from a user perspective.