Skip to content

Map context bounds to context parameters #8055

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

Closed
wants to merge 22 commits into from

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Jan 21, 2020

Before they were mapped to implicit parameters.
Exception: Under -language:Scala2Compat, accept
explicit regular arguments for them but emit a
warning and offer a patch that inserts a .with.

Based on #8017

This reverts commit d1579e6.

# Conflicts:
#	compiler/src/dotty/tools/dotc/parsing/Parsers.scala
#	docs/docs/internals/syntax.md
#	tests/pos/reference/delegates.scala
Was updated to new syntax by accident
Changes should be rolled out only after released.
For given instances:

    given ...

For context parameters

    ... with ...

For context functions

    A ?=> B
It's now
```scala
given _
given T
```
Thta way it's more regular: A given selector is always followed by something: Either
a wildcard or a type.

The previous syntax for type bounds on normal imports is no longer supported.
We might want to bring it back at some point, but it's not essential.
There are valid use cases, and syntactic awkwardness can be kept in check
by the "one space following a with clause" rule.
Address comments by @soronpo
Before they were mapped to implicit parameters.
Exception: Under -language:Scala2Compat, accept
explicit regular arguments for them but emit a
warning and offer a patch that inserts a `.with`.
Copy link
Member

@dottybot dottybot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Commit Messages

We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).

Please stick to these guidelines for commit messages:

  1. Separate subject from body with a blank line
  2. When fixing an issue, start your commit message with Fix #<ISSUE-NBR>:
  3. Limit the subject line to 72 characters
  4. Capitalize the subject line
  5. Do not end the subject line with a period
  6. Use the imperative mood in the subject line ("Add" instead of "Added")
  7. Wrap the body at 80 characters
  8. Use the body to explain what and why vs. how

adapted from https://chris.beams.io/posts/git-commit

Have an awesome day! ☀️

@odersky
Copy link
Contributor Author

odersky commented Jan 22, 2020

It's too early to do it now, as witnessed by the community build failures. We'll change for 3.1 instead. This has been rolled into #8027

@odersky odersky closed this Jan 22, 2020
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.

2 participants