Skip to content

Commit

Permalink
Fix typos.
Browse files Browse the repository at this point in the history
  • Loading branch information
zhongl committed Nov 9, 2024
1 parent 8a3f375 commit 407dacb
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/_docs/contributing/architecture/types.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ Ground Type has no meaningful underlying type, typically it is the type of metho
definitions, but also union types and intersection types, along with utility types of the
compiler.

Here's a diagram, serving as the mental model of the most important and distinct types available after the `typer` phase, derived from [dotty/tools/dotc/core/Types.scala][1]:
Here's a diagram, serving as the mental model of the most important and distinct types available after the `typer` phase, derived from [Types.scala]:

```
Type -+- proxy_type --+- NamedType --------+- TypeRef
Expand Down
2 changes: 1 addition & 1 deletion docs/_docs/internals/gadts.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ Right now, we record GADT constraints for:
- function/method type parameters
- class type parameters

There is a branch on the way which will also record them for type members (so path-dependent types) and singleton types. It has a paper associated: "Implementing path-depepdent GADTs for Scala 3".
There is a branch on the way which will also record them for type members (so path-dependent types) and singleton types. It has a paper associated: "Implementing path-dependent GADTs for Scala 3".

### What are necessary relationships? Any examples?

Expand Down

0 comments on commit 407dacb

Please sign in to comment.