Document how to use from Typelevel toolkit from REPL

[armanbilge]

• Scala-cli REPL with Toolkit scala/toolkit#37

[zetashift]

What is the incantation for this?

❯ scala-cli repl --with-toolkit=typelevel:toolkit
Downloading 3 dependencies and 2 internal dependencies
[error]  Error downloading org.typelevel:toolkit_3:toolkit
[error]   not found: /home/rishi/.ivy2/local/org.typelevel/toolkit_3/toolkit/ivys/ivy.xml
[error]   not found: https://repo1.maven.org/maven2/org/typelevel/toolkit_3/toolkit/toolkit_3-toolkit.pom
[error]   not found: /home/rishi/.cache/scalacli/local-repo/1.0.5/org.typelevel/toolkit_3/toolkit/ivys/ivy.xml
[error]   No fallback URL found
[error] COMMAND_LINE
[error]  Error downloading org.typelevel:toolkit-test_3:toolkit
[error]   not found: /home/rishi/.ivy2/local/org.typelevel/toolkit-test_3/toolkit/ivys/ivy.xml
[error]   not found: https://repo1.maven.org/maven2/org/typelevel/toolkit-test_3/toolkit/toolkit-test_3-toolkit.pom
[error]   not found: /home/rishi/.cache/scalacli/local-repo/1.0.5/org.typelevel/toolkit-test_3/toolkit/ivys/ivy.xml
[error]   No fallback URL found

EDIT: got it!

 scala-cli repl --toolkit=typelevel:latest

[TonioGela]

WOW! we definitively need that kitchen sink import now :D

[zetashift]

WOW! we definitively need that kitchen sink import now :D

This was exactly my first thought as well!! How cool of a reply experience would that be.

Tho I believe we still need to do unsafeRunSync everywhere no?

[armanbilge]

Tho I believe we still need to do unsafeRunSync everywhere no?

Yeah, this is annoying 😒 it's just how it is tho. I guess the REPL-sink import should bring in the implicit runtime that it Just Works:tm:.

[TonioGela]

Tho I believe we still need to do unsafeRunSync everywhere no?

Yeah, this is annoying 😒 it's just how it is tho. I guess the REPL-sink import should bring in the implicit runtime that it Just Works™️.

We can probably namespace the imports then: we can have an import org.typelevel.toolkit.* that is the scripts' kitchen sink import and a import org.typelevel.toolkit.repl.* that extends it with the required implicit (import cats.effect.unsafe.implicits.*).

And now we just need finishing the discussion in #2 :D

[EDIT] There won't be anything preventing the users from importing the repl package in scripts though 🤔 Also, the tooling might get confused.

[zetashift]

It might still be worth it imho, e.g. imagine being able to use it in Markdown: https://scala-cli.virtuslab.org/docs/guides/markdown/

and then you could have some runbook that deploys stuff in the markdown file with docs etc all using IO! Or any other literate programming thingy.
Maybe hook-up a frontend and to it and serve a notebook-type of environment even...
IMHO, it makes a lot of sense to atleast experiment with it.

[SethTisue]

as of Scala 3.8, one can also ask for the toolkit after starting the REPL:

Welcome to Scala 3.8.3 (21.0.10, Java OpenJDK 64-Bit Server VM).
Type in expressions for evaluation. Or try :help.
                                                                                                    
scala> :dep org.typelevel::toolkit:0.2.0
Resolved 1 dependencies (46 JARs)
                                                                                                    
scala> import cats.effect.unsafe.implicits.*

though writing latest instead of 0.2.0 doesn't work, not sure if that should be expected to work