Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Generate .semanticidx files for SemanticDB outputs #199

Closed
xeno-by opened this issue Aug 19, 2018 · 1 comment
Closed

Generate .semanticidx files for SemanticDB outputs #199

xeno-by opened this issue Aug 19, 2018 · 1 comment
Assignees
@xeno-by
Labels
SemanticDB
Milestone
M4

Comments

@xeno-by
Copy link
Contributor

xeno-by commented Aug 19, 2018 •
edited
Loading

Currently, Rsc only generates .semanticdb files as its output. However, Rsc doesn't accept pure .semanticdb files as its output - it wants .semanticdb + .semanticidx. This means that we can't yet have Rsc-based targets depend on Rsc-based targets, which probably needs to be fixed.
@xeno-by xeno-by added this to the M4 milestone Aug 19, 2018
@xeno-by xeno-by self-assigned this Aug 19, 2018
@xeno-by
Copy link
Contributor Author

xeno-by commented Aug 20, 2018

I've been able to work around this by calling Metai on the results of running Rsc. That is suboptimal performance-wise, but that unblocks our M4 work, so I'm going to unassign the M4 milestone from this ticket.

@xeno-by xeno-by removed this from the M4 milestone Aug 20, 2018
@xeno-by xeno-by removed their assignment Sep 13, 2018
@xeno-by xeno-by added this to the M4 milestone Oct 9, 2018
@xeno-by xeno-by self-assigned this Oct 9, 2018
xeno-by added a commit to xeno-by/rsc that referenced this issue Oct 9, 2018
@xeno-by
Generate .semanticidx files for SemanticDB outputs (fix twitter#199)
a8e66ee
@xeno-by xeno-by closed this as completed Oct 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xeno-by xeno-by

Labels
SemanticDB
Milestone
M4
Development

No branches or pull requests
1 participant
@xeno-by