We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[reuillon:~/Projects/gridscale] master(+63/-57,1) ± scala3-repl --version Scala code runner version 3.0.1 -- Copyright 2002-2021, LAMP/EPFL
manifest[String]
1 |manifest[String] | ^ | No Manifest available for String.
A manifest for the type String
The text was updated successfully, but these errors were encountered:
For now, there is no support for summoning Manifest instances in scala 3. As a workaround for most use cases, you can use ClassTag.
Manifest
Sorry, something went wrong.
Also, there was a discussion under #9482, which is sort of relevant.
We could keep this open as #9482 is about summoning OptManifest, this is for summoning Manifest, or we keep one?
OptManifest
let's close in favor of #9482, if we can do one we can do the other.
As a workaround for most use cases, you can use ClassTag.
In fact it's more than a workaround, please treat Manifest as deprecated and use ClassTag instead.
bishabosha
No branches or pull requests
Compiler version
[reuillon:~/Projects/gridscale] master(+63/-57,1) ± scala3-repl --version Scala code runner version 3.0.1 -- Copyright 2002-2021, LAMP/EPFL
Minimized code
manifest[String]
Output
Expectation
A manifest for the type String
The text was updated successfully, but these errors were encountered: