-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add Enum Eq #2552
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
Merged
Merged
Add Enum Eq #2552
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
8a60a20
Make hasEq look in implicit scope even if an eqAny is visible
odersky a718213
Make enums implement Eq
odersky 6654f76
Fixes to hasEq
odersky 613ff30
Add test case that eqAny unimport works
odersky 961b9ef
Fix comparisons for primitive types
odersky 70b2f38
Add decsription of Eq desugarings for enums
odersky d6f4088
Section on multiversal equality
odersky 79e6b51
Section on type lambdas
odersky 1d4c392
Add section on auto-tupling of function parameters
odersky e9d87e0
Add section on named type arguments
odersky 0824df5
Harmonize types before checking can equals in pattern match
odersky 3092341
Fix typo
odersky bcaaa38
Add section on implicit function types
odersky df75369
Temporary fix for test case
odersky b0e548e
Fix for test cases
odersky fa420fe
Fix typo
odersky 5b7406f
New section on inline
odersky bce0df9
Fix neg tests
odersky File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
--- | ||
layout: doc-page | ||
title: "Automatic Tupling of Function Parameters" | ||
--- | ||
|
||
Say you have a list of pairs | ||
|
||
val xs: List[(Int, Int)] | ||
|
||
and you want to map `xs` to a list of `Int`s so that eich pair of numbers is mapped to | ||
their sum. Previously, the best way to do this was with a pattern-matching decomposition: | ||
|
||
xs map { | ||
case (x, y) => x + y | ||
} | ||
|
||
While correct, this is also inconvenient. Dotty now also allows: | ||
|
||
xs.map { | ||
(x, y) => x + y | ||
} | ||
|
||
or, equivalently: | ||
|
||
xs.map(_ + _) | ||
|
||
Generally, a function value with `n > 1` parameters is converted to a | ||
pattern-matching closure using `case` if the expected type is a unary | ||
function type of the form `((T_1, ..., T_n)) => U`. | ||
|
||
|
||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,99 @@ | ||
--- | ||
layout: doc-page | ||
title: "Implicit Function Types" | ||
--- | ||
|
||
An implicit funciton type describes functions with implicit parameters. Example: | ||
|
||
type Contextual[T] = implicit Context => T | ||
|
||
A value of implicit function type is applied to implicit arguments, in | ||
the same way a method with implicit parameters is applied. For instance: | ||
|
||
implicit ctx: Context = ... | ||
|
||
def f(x: Int): Contextual[Int] = ... | ||
|
||
f(2) // is expanded to f(2)(ctx) | ||
|
||
Conversely, if the expected type of an expression `E` is an implicit | ||
function type `implicit (T_1, ..., T_n) => U` and `E` is not already an | ||
implicit function value, `E` is converted to an implicit function value | ||
by rewriting to | ||
|
||
implicit (x_1: T1, ..., x_n: Tn) => E | ||
|
||
where the names `x_1`, ..., `x_n` are arbitrary. For example, continuing | ||
with the previous definitions, | ||
|
||
def g(arg: Contextual[Int]) = ... | ||
|
||
g(22) // is expanded to g { implicit ctx => 22 } | ||
|
||
g(f(2)) // is expanded to g { implicit ctx => f(2)(ctx) } | ||
|
||
g(implicit ctx => f(22)(ctx)) // is left as it is | ||
|
||
Implicit function types have considerable expressive power. For | ||
instance, here is how they can support the "builder pattern", where | ||
the aim is to construct tables like this: | ||
|
||
table { | ||
row { | ||
cell("top left") | ||
cell("top right") | ||
} | ||
row { | ||
cell("botttom left") | ||
cell("bottom right") | ||
} | ||
} | ||
|
||
The idea is to define classes for `Table` and `Row` that allow | ||
addition of elements via `add`: | ||
|
||
class Table { | ||
val rows = new ArrayBuffer[Row] | ||
def add(r: Row): Unit = rows += r | ||
override def toString = rows.mkString("Table(", ", ", ")") | ||
} | ||
|
||
class Row { | ||
val cells = new ArrayBuffer[Cell] | ||
def add(c: Cell): Unit = cells += c | ||
override def toString = cells.mkString("Row(", ", ", ")") | ||
} | ||
|
||
case class Cell(elem: String) | ||
|
||
Then, the `table`, `row` and `cell` constructor methods can be defined | ||
in terms of implicit function types to avoid the plumbing boilerplate | ||
that would otherwise be necessary. | ||
|
||
def table(init: implicit Table => Unit) = { | ||
implicit val t = new Table | ||
init | ||
t | ||
} | ||
|
||
def row(init: implicit Row => Unit)(implicit t: Table) = { | ||
implicit val r = new Row | ||
init | ||
t.add(r) | ||
} | ||
|
||
def cell(str: String)(implicit r: Row) = | ||
r.add(new Cell(str)) | ||
|
||
With that setup, the table construction code above compiles and expands to: | ||
|
||
table { implicit $t: Table => | ||
row { implicit $r: Row => | ||
cell("top left")($r) | ||
cell("top right")($r) | ||
}($t) | ||
row { implicit $r: Row => | ||
cell("botttom left")($r) | ||
cell("bottom right")($r) | ||
}($t) | ||
} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason to not use semantic names here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we could do that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the other hand, maybe it's not worth the hassle. The names literally don't matter.