Skip to content

Fix #2180: Docs update #2422

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 7 commits into from
May 15, 2017
Merged

Fix #2180: Docs update #2422

merged 7 commits into from
May 15, 2017

Conversation

biboudis
Copy link
Contributor

No description provided.

@biboudis biboudis requested review from smarter and felixmulder May 12, 2017 14:32
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! ❤️

Have an awesome day! ☀️

@smarter
Copy link
Member

smarter commented May 12, 2017

@felixmulder Looks like the dotty-bot disagrees with itself on whether the CLA is signed or not :)


If you are interested in debugging the compiler you can enable the necessary agent on the JVM and this
is done in two steps. For the first step you need to pass the
necessary flag to the running VM. For convenience, this is already in comments on the `Build.scala` file under project.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe explain in more details what line to uncomment?


Index
-----
* Usage
Copy link
Member

Choose a reason for hiding this comment

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

While you're at it, could you add a link to https://github.com/lampepfl/dotty/blob/master/docs/docs/contributing/backend.md in the Contributing section of the table of content? I forgot to add it before.

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done!


2. It is recommended to change the default output folder (in `Properties > java
Assuming you have cloned dotty's repository from Github (and run `sbt managedSources` as described in
Copy link
Member

Choose a reason for hiding this comment

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

For Eclipse, you need to run sbt ;managedSources;eclipse

Copy link
Member

Choose a reason for hiding this comment

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

This point still needs to be fixed

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added the sbt eclipse in the line below!

Copy link
Member

Choose a reason for hiding this comment

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

I don't see it?

Copy link
Member

@smarter smarter left a comment

Choose a reason for hiding this comment

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

Awesome!

2. It is recommended to change the default output folder (in `Properties > java
Assuming you have cloned dotty's repository from Github (and run `sbt managedSources` as described in
[Getting Started](getting-started.md)) you can now proceed to set up Dotty with Eclipse. In addition to the previous
command you need to run `sbt eclipse` to generate the project structure for Eclipse.
Copy link
Contributor Author

@biboudis biboudis May 12, 2017

Choose a reason for hiding this comment

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

ping @smarter

Copy link
Member

Choose a reason for hiding this comment

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

Ah I see now, thanks. But I would prefer to not leave this critical command inside a line of text, I think it'd be better to have it in a real code block.

Copy link
Member

Choose a reason for hiding this comment

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

Basically something like:

1. Follow the instructions in the [Getting Started](...) page
2. Generate the Eclipse configuration files:
```
sbt eclipse
```

Copy link
Contributor

@felixmulder felixmulder left a comment

Choose a reason for hiding this comment

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

Excellent job! We have real docs now! 🎉

2. Generate the Eclipse configuration files:
```
sbt eclipse
```
Copy link
Contributor

Choose a reason for hiding this comment

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

This one doesn't have the nice ```shell and $ as your previous snippets (=


1. Open New Project dialog and select `Scala` > `Dotty`
2. Proceed as usual and don't forget to create or select Dotty SDK.
Assuming you have cloned dotty's repository from Github (and run `sbt managedSources` as described in [Getting Started](getting-started.md))
Copy link
Contributor

Choose a reason for hiding this comment

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

, at the end of this line for inner voice to be able to take a breath.

```

You can further restrict the executed tests to a subset of `TestClass` methods
as follows:
To run a single test class you use `testOnly` and the fully qualified class name.
Copy link
Contributor

Choose a reason for hiding this comment

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

Actually, you can do:

> testOnly -- *targetFunction

to run all tests named targetFunction, in any class.

You can also do:

> testOnly *.MyTargetClass

to run all paths with a class named MyTargetClass. Both sides are regexes, so you should be able to do:

> testOnly * -- *

which would be the same as test.

> partest-only-no-bootstrap
> partest-only
> partest
> dotty-compiler/testOnly dotty.tools.dotc.transform.TreeTransformerTest -- *canOverwrite
Copy link
Contributor

Choose a reason for hiding this comment

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

This could be written shorter as: testOnly *.TreeTransformerTest -- *canOverride, but I guess it's good to be consequential to what you decided to do WRT the above comment :)

- reuses the same VM for compilation
- allows filtering of tests
- runs much faster (almost 2x)
All of these tests are contained in the `./tests/*` directories.

Currently to run these tests you need to invoke from sbt:

```bash
> testOnly dotty.tools.dotc.CompilationTests
Copy link
Contributor

Choose a reason for hiding this comment

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

this is aliased as: vulpix without args.

@@ -78,7 +50,7 @@ scala> import dotty.tools.DottyTypeStealer._; import dotty.tools.dotc.core._; im

Now, you can define types and access their representation. For example:

```scala
```bash
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm pretty sure this was to get nicer syntax-highlighting. But I'm not sure I'm the one who wrote it..

Copy link
Contributor Author

Choose a reason for hiding this comment

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

restored!

@felixmulder
Copy link
Contributor

@biboudis: the bot could not verify your CLA signature. I checked it manually, and it looks like you haven't signed: https://www.lightbend.com/contribute/cla/scala/check/biboudis

Please sign: https://www.lightbend.com/contribute/cla/scala

@felixmulder felixmulder merged commit c6a2a3f into scala:master May 15, 2017
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.

4 participants