Skip to content

Conversation

@adriaanm
Copy link
Contributor

@adriaanm adriaanm commented Mar 12, 2019

Ref scala/scala-dev#441

Delay deprecation proposed in #7662 to 2.14.

@scala-jenkins scala-jenkins added this to the 2.13.1 milestone Mar 12, 2019
@adriaanm adriaanm modified the milestones: 2.13.1, 2.13.0-RC1 Mar 12, 2019
@som-snytt
Copy link
Contributor

som-snytt commented Mar 12, 2019

s/proposed/foisted to use the term from classical logic.

Sorry a module system based on package objects will have to wait for 2.17.

@lrytz lrytz merged commit ad1cfe2 into scala:2.13.x Mar 13, 2019
@neko-kai
Copy link
Contributor

@som-snytt
Might as well propose your design instead of being snarky. Maybe it's worth giving up package objects for ;)

@som-snytt
Copy link
Contributor

@Kaishh it's a follow-up to my comment when I approved the proposal PR.

@neko-kai
Copy link
Contributor

neko-kai commented Mar 13, 2019

@som-snytt
If you mean the following comment, it's a bit too vague.

The best part is that it blows the future wide open to re-introduce package objects as a module system.

Scala's objects and package objects already form a very powerful module system, a clarification might help convey what system you envision exactly.

@som-snytt
Copy link
Contributor

(I never answered the question what are package objects good for. I always liked the original idea to use them to define API, like exports. I wonder if they could have interacted with Java modules.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants