Skip to content

use point positions in comment index #274

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 3 commits into from
Mar 16, 2021
Merged

use point positions in comment index #274

merged 3 commits into from
Mar 16, 2021

Conversation

lrytz
Copy link
Contributor

@lrytz lrytz commented Mar 11, 2021

fixes #220

i only tested this on 2.13.5 locally, let's see what travis says.

@lrytz
Copy link
Contributor Author

lrytz commented Mar 12, 2021

@raboof this went green. not sure what's the best strategy for testing, i added a commit that tests everything with -Yrangepos. I think either the test suite should just use the compiler's default (so rangepos will be on for 2.13.4+), or everything should be tested twice (with and without rangepos).

@lrytz lrytz requested a review from raboof March 12, 2021 08:19
Copy link
Contributor

@raboof raboof left a comment

Choose a reason for hiding this comment

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

I won't pretend I understand the logic/internals here, but the change looks neat, and the tests give confidence ;)

not sure what's the best strategy for testing, i added a commit that tests everything with -Yrangepos. I think either the test suite should just use the compiler's default (so rangepos will be on for 2.13.4+), or everything should be tested twice (with and without rangepos).

TBQH I'd be fine with just testing everything with -Yrangepos, as that's what we're recommending going forward. If people run into trouble without it they can add -Yrangepos or upgrade to a newer Scala version... WDYT?

@lrytz
Copy link
Contributor Author

lrytz commented Mar 12, 2021

In this case I'd suggest to remove the rangepos overrides in the tests, so that it tests the compiler's default.

@lrytz
Copy link
Contributor Author

lrytz commented Mar 12, 2021

@raboof could you test this on Akka (2.12.13, 2.13.3, 2.13.5)? Would you prefer to have a release or do your own publishLocal?

@lrytz
Copy link
Contributor Author

lrytz commented Mar 12, 2021

(failure seems spurious, and travis doesn't let me restart the job, "Oh no! An error occurred. The job could not be restarted")

@raboof
Copy link
Contributor

raboof commented Mar 12, 2021

@raboof could you test this on Akka (2.12.13, 2.13.3, 2.13.5)? Would you prefer to have a release or do your own publishLocal?

I'll give it a go (with publishLocal)

@lrytz
Copy link
Contributor Author

lrytz commented Mar 12, 2021

Thanks!

@raboof
Copy link
Contributor

raboof commented Mar 12, 2021

Tested a couple of variations:

With genjavadoc 0.16 and default settings:

  • 2.12.13 and 2.13.3: ok, 2.13.5 not ok (as expected)
    With genjavadoc 0.16, enabling -Yrangepos explicitly:
  • 2.12.13 and 2.13.3: both not ok (as expected)

With this branch and default settings:

  • 2.12.13, 2.13.3 and 2.13.5 all ok
    With this branch, enabling -Yrangepos explicitly:
  • 2.12.13 and 2.13.3 both ok

So all good!

@lrytz
Copy link
Contributor Author

lrytz commented Mar 16, 2021

Thanks for testing it!

@lrytz lrytz merged commit 52b8fdb into lightbend:master Mar 16, 2021
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.

Problems when running with -Yrangepos
2 participants