- Notifications
You must be signed in to change notification settings - Fork1k
language tour: improve Traits page#3232
New issue
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
547bba0 tofe643f8CompareSethTisue commentedNov 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I'll have to figure out how to get the Scala-3-only example past mdoc — probably by making Scala 3 the default language version for mdoc. |
bishabosha commentedNov 23, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I had an exploration of switching mdoc to scala 3 - basically a lot of localized pages either need updating or mdoc turned off. See here:main...bishabosha:docs.scala-lang:mdoc-use-scala3 My process was iterate running |
SethTisue commentedNov 24, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@bishabosha I think we could reasonably just disable mdoc on the localized pages; many of them are quite out of date anyway for any particular language, if a motivated volunteer wanted to do the work necessary to reenable mdoc for that language's pages, they could do so; we could open a "help wanted" issue on it and/or could we have a magic comment or magic metadata on the top of certain pages to mark them as needing to be run with Scala 2 instead? |
fixes#3097