Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Justin Kaeser
    @jastice
    yes, and any feedback as to where the implementation falls short would be helpful for spec development
    Tobias Roeser
    @lefou
    How to support more languages in mill.contrib.BSP ?
    Tobias Roeser
    @lefou
    Hm, mill.contrib.BSP with IJ seems to not work so well in it's current state. I tried to open a mostly-Java project (some modules are also AspectJModules) but all imports from dependencies are red. Also build.sc itself is very red.
    Justin Kaeser
    @jastice
    we'll need to check that out. did it work for Mill itself for you? maybe there's been some changes causing breakage
    Tobias Roeser
    @lefou
    I'll check ...
    Justin Kaeser
    @jastice
    we might have to define some bsp extensions for Mill and Java
    Tobias Roeser
    @lefou
    How to reach the "import project..." action once IJ is already open (with another project) ?
    Justin Kaeser
    @jastice
    file / new project from existing sources
    Tobias Roeser
    @lefou
    Thanks
    Tobias Roeser
    @lefou
    With mill itself it looks a bit better. Some sources resolve their imports. build.sc stays red though
    Not only the $ivy imports but also the mill API
    Justin Kaeser
    @jastice
    yeah, we might want to add some dedicated support
    Eric Peters
    @er1c
    @jastice FYI, upgraded to latest and still broken, but not sure if it was fixed that soon :)
    Gavin Bisesi
    @Daenyth
    Is there a way I can make intellij's compiler output not clash with sbt's?
    It's such a pain if I compile in one the other needs a from-scratch rebuild
    Justin Kaeser
    @jastice
    you can use sbt shell for building from intellij
    Gavin Bisesi
    @Daenyth
    and if I prefer not to?
    There must be some way to improve intellij's behavior there
    Justin Kaeser
    @jastice
    maybe changing project structure / project settings -> project compiler output?
    Gavin Bisesi
    @Daenyth
    sounds promising
    Justin Kaeser
    @jastice
    but then the modules must be set to "inherit project compile output path", otherwise they use the path imported from sbt
    Pavel Fatin
    @pavelfatin

    We added basic Dotty support in the IntelliJ Scala plugin a long time ago, right after the announcement of Dotty. However, for a long time Dotty has been a dark horse, and aiming at a moving target hadn't been easy. So it was reasonable to put that task on the back-burner and focus on Scala 2 for a while. Now that Dotty is finally destined to become Scala 3 and the language features are getting more stable, we have started to work on a full-fledged Scala 3 support.

    The 2020.1 Scala plugin nightly builds now include preliminary support of Scala 3: the new syntax (by the way, we had to adjust that "given" thing several times already :) ), error highlighting, navigation, type info, and many other bread-and-butter IDE features. Although the functionality is already usable, it is still "in beta" - some bumps here and there are expected. We depend on your feedback to smooth the rough edges and make Scala 3 support as good as Scala 2 one (and possibly even better, because, just as Dotty, we now have a lot of experience to rely on).

    Trying the nightly builds is easy:

    1. Download https://www.jetbrains.com/idea/nextversion (you may also do that via Settings | Appearance | System | Updates)
    2. Open Settings | Languages | Scala | Updates
    3. Select "Nightly" plugin update channel and press "Check for updates"
      (You can always select "EAP" or "Release" to revert to a more stable build; alternatively, you can download any Scala plugin build from https://plugins.jetbrains.com/plugin/1347-scala/versions)

    If you haven't yet tried Dotty, now is as good time as ever - clone the https://github.com/lampepfl/dotty-example-project and open it in IntelliJ IDEA. Your feedback is very welcome, as always.

    IntelliJ Scala plugin team

    Oron Port
    @soronpo
    :clap:
    Hanns Holger Rutz
    @Sciss
    :tada:
    Dale Wijnand
    @dwijnand
    Nice work, Pavel!
    Lukas Rytz
    @lrytz
    🥳
    Rafael Merino García
    @imrafaelmerino
    I just tried it out on a project I migrated to Dotty with all its brand new features and it looks great! Thanks!
    Wojtek Pituła
    @Krever
    @pavelfatin That great news. Should I see dotty anywhere in new project dialog or it's not yet implemented?
    Pavel Fatin
    @pavelfatin
    There's no "Scala 3" in Project Wizard yet (the work is in progress), but it should be possible to open an existing Scala 3 project.
    Eric Peters
    @er1c
    @jastice runConfigurations are back, thanks!
    Justin Kaeser
    @jastice
    no thanks to me!
    ruslan
    @unoexperto
    @pavelfatin Are "givens" supposed to work ? Majority of classes from dotty-example-project project have parsing errors for me.
    image.png
    @pavelfatin For example in AutoParamTupling there is "too many parameters" error:
    image.png
    Cannot parse givens in Conversion:
    image.png
    Cannot parse enums in EnumTypes
    ruslan
    @unoexperto
    image.png
    Cannot parse intersection types in IntersectionTypes
    Am I missing anything ? I'm on 2020.1 EAP with nightly Scala plugin
    Pavel Fatin
    @pavelfatin
    @unoexperto Please try to re-import the sbt project (via sbt tool window)
    ruslan
    @unoexperto
    @pavelfatin Oh wow. Everything is clean! Impressive work, guys. When are you estimating to be officially done with Scala 3 support ?
    Rafael Merino García
    @imrafaelmerino
    in my project, everything is clean as well and I'm using given, using, if-then-else, no new keyword when possible and indentation over curly braces
    Pavel Fatin
    @pavelfatin
    We may announce the support officially in the 2020.1 release. As to when it's "done" - it's not that simple, and, to some extent, depends on Scala 3 itself (it's still under heavy development).
    Pavel Fatin
    @pavelfatin

    @unoexperto

    Hey guys. I'm trying dotty-example-project with new IDEA pluging and not sure if it's plugin or my code that is problem.
    In ContextQueries.scala lines 42,43 code doesn't see implicit executing context.
    Importing scala.concurrent.ExecutionContext.global in scope doesn't help.
    How is it supposed to work now ?

    (It's probably reasonable to use the "intellij-scala" Gitter rather than the "dotty" one)

    "doesn't see implicit executing context" - i.e. there's red code or...?

    ruslan
    @unoexperto
    @pavelfatin I figured it out. What happened is moving files to new package silently removed import ExecutionContext.Implicits.global line in ContextQueries class.
    @pavelfatin Perhaps IDEA should not modify imports when moving classes from one package to another ?
    Pavel Fatin
    @pavelfatin
    Definitely. Thanks for the info!
    Hanns Holger Rutz
    @Sciss
    I usually leave the default of IntelliJ watching build.sbt and asking me if I want to import the changes (so this is manual confirmation not auto-import). I have one project though, where I must have checked some "never" box, and so it doesn't seem to watch build.sbt (so I have to open sbt settingsand refresh explicitly every time); I searched through the preferences and project settings, and could not spot where this setting is saved. Can I reset the default behaviour without having to wipe the .idea directory?