Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 13 2018 14:13
    User @SethTisue unbanned @viju0731_twitter
  • Nov 13 2018 14:11
    @SethTisue banned @viju0731_twitter
Andriy Plokhotnyuk
@plokhotnyuk
:+1:
darjutak
@darjutak
Thanks, @soronpo!
Dhash Shrivathsa
@DhashS
thanks @soronpo ! these are awesome videos. Thanks @darjutak, i'm going to have enough entertainment for a month :)
Martijn Hoekstra
@martijnhoekstra
what's the status of the SIP process nowadays?
Does it still run?
I believe this SIP is released
so I'm not sure what should happen with the SIP. Should it be numbered and accepted retroactively? Discarded?
Martijn Hoekstra
@martijnhoekstra
Still discussing it seems silly, considering it has already been released.
Oron Port
@soronpo
@darjutak ^
darjutak
@darjutak
Hey @martijnhoekstra , thanks for the question. The answer goes like this: now that I am done with ScalaDays (even though I am still working on final reports, closing accounts and so forth) I will dedicate my time more to SIP. This includes 1) writing all the minutes I owe (many I might add, and am very sad I am behind); 2) giving an overview "where we stand and what is to be expected"; 3) scheduling the next meeting for the end of August, as everyone is now in vacation.
Martijn Hoekstra
@martijnhoekstra
that sounds great @darjutak
darjutak
@darjutak
To answer your question more precisely: yes, it still runs, the last one took place just before ScalaDays in June
it was face-to-face (third one of such kind)
Martijn Hoekstra
@martijnhoekstra
that's good to hear. It's still the temporary process of the scala3 SIPs, with all other SIPs on hold?
darjutak
@darjutak
well, I did bring that up to the SIP committee some time ago - and the conclusion is that previous SIPs need to be discussed and action needs to take place
so they are not on hold, and as of August we will integrate those too
Martijn Hoekstra
@martijnhoekstra
that all sounds really good
thanks again for your efforts in these processes -- there is so much process and so little staff funding to go around, I really appreciate all the hard work
darjutak
@darjutak
Thank you, @martijnhoekstra very much for your kind words!!!
Oron Port
@soronpo
@darjutak I think most of us are primarily interested in the bottom line status of the SIPs, so if that can be published before the minutes, it will be much appreciated (and I think it's quicker and less frustrating to do).
darjutak
@darjutak
@soronpo I agree, but still, I need to focus on it, so not before the end of next week. We have 2 minutes ready, March and June (the face-to-face ones) which will already be a huge chunk + I will create a simple overview, as per your advice, but please bear with me (o:
Rob Norris
@tpolecat
Where did scala/scala-collection-contrib come from?
It's the first I have heard about it.
Modulo my bad memory.
Ichoran
@Ichoran
It came from proposals for collections that weren't so obviously desperately needed in the standard library that we wanted to just stick an unproven collection in there for 2.13.
It was part of the collections rework for 2.13.
I think collections-incubator is a more accurate way to think about it.
Rob Norris
@tpolecat
I see, ok.
Guillaume Martres
@smarter
collections-purgatory
Ichoran
@Ichoran
Haha
Andreas Gies
@atooni

Hello, I hope I am hitting the right channel. In the last couple of days I have given scala-metals a spin with VSC and I did really like the editing experience. I have then tried to use the same work mode I was using with IntelliJ: When I work on a particular change I like to start sbt in watcher mode and start by writing the tests for the thing I want to change. Then I start changing the code and with every save the tests are executed.

When I do the same with metals / VSC the workflow seems to work, but I am under the impression that code changes are not picked up by VSC anymore as soon as I start sbt externally in watching mode.

My question now is if that is a valid setup at all ? - Should I use a different approach ? - What are you guys doing normally ?

Thanks in advance
Andreas

Seth Tisue
@SethTisue
@atooni try the scalameta/metals room
Andreas Gies
@atooni
Ok - will do - thank you
nafg
@nafg
In the future could the videos not have a red stripe at the bottom? It makes it hard to see the YouTube indicator of what you already watched.
nafg
@nafg
I fixed it with turnStyle extension and #progress.ytd-thumbnail-overlay-resume-playback-renderer { background-color: #FF7700; } ;)
(a little close to red still but whatever)
Michael Wizner
@mwz
Hi everyone it seems that Scalastyle has been left without any active maintainers and there is no one in the scalastyle org on Github who is willing to make a new release and look after this project. Is that something that someone from Scala Center could help to sort out given the wide adoption of this project in the Scala ecosystem? Would you guys consider forking this project under Scala Center with a new set of maintainers who are willing to step up and actively maintain and push this project forward?
Rob Norris
@tpolecat
I think scalafix should probably subsume scalastyle and wartremover and I agree writing linting rules might be a sensible SC project.
I have a list of this sort of thing that I’d like to bring up at the next meeting.
Seth Tisue
@SethTisue
advisory board minutes, w/ Seb's report on Center activities: https://twitter.com/scala_lang/status/1161143590489190400
Martijn Hoekstra
@martijnhoekstra
I for one welcome our new hoody overlord.
Seth Tisue
@SethTisue
added https://github.com/scalacenter/advisoryboard/blob/master/proposals/README.md with status of all the Scala Center proposals
Guillaume Martres
@smarter
The status of 011-debugging-symbols.md is incorrect, see scala/scala.epfl.ch#47
Seth Tisue
@SethTisue
@smarter thanks for the ping, I'll work with Seb to get that resolved
Guillaume Martres
@smarter
cheers
consolidation would be nice (move all issues to scala/, close issues on scalacenter/)
or even delete the scalacenter/ fork
Julien Richard-Foy
@julienrf