-
Notifications
You must be signed in to change notification settings - Fork 1k
Scala standard library: SIP or SPP? #943
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@SethTisue IIRC, the consensus is that the SIP Committee is in charge of the to-be Scala Core, whereas anything considered previously part of the Scala Library will be under control of the SPP Committee. Does this sound reasonable? |
I’d say the standard library is part of the core, once we’re done
modularising in 2.13
…On Sat, Dec 2, 2017 at 15:23 Jorge ***@***.***> wrote:
@SethTisue <https://github.com/sethtisue> IIRC, the consensus is that the
SIP Committee is in charge of the to-be Scala Core, whereas anything
considered previously part of the Scala Library will be under control of
the SPP Committee. Does this sound reasonable?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#943 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFjywn6aPPh2F6qvYlJA1HQQRHMQl_xks5s8dvigaJpZM4QzbrW>
.
|
it sounds like we're all on the same page here. I'll make a PR proposing alternate wording on that page |
PR #958 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
http://docs.scala-lang.org/sips/index.html has the Scala standard library as under the control of the SPP committee. Is that really the case? My understanding was that since SLIP was shut down, the core Scala standard library went back under SIP, and that SPP covers everything but scala-library.jar.
(@jvican? @adriaanm?)
The text was updated successfully, but these errors were encountered: