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

Figure out how to properly handle an underlying function change and staleness propagation #17

Open
Norbo11 opened this issue Apr 15, 2019 · 1 comment
Open

Figure out how to properly handle an underlying function change and staleness propagation #17

Norbo11 opened this issue Apr 15, 2019 · 1 comment
Labels
enhancement Small feature or request

Comments

@Norbo11
Copy link
Owner

Norbo11 commented Apr 15, 2019

No description provided.

@Norbo11
Copy link
Owner Author

Norbo11 commented Apr 15, 2019

Right now, we are only "stale" on a new commit.

The most conservative approach would mark everything stale as soon as a single character change is made.

Somewhere in between is using the PSI engine to propagate staleness to all callers of whatever we are editing. But this doesn't cover every scenario... try to come up with a counter example.

@Norbo11 Norbo11 changed the title Figure out how to properly handle an underlying function change and staleness Figure out how to properly handle an underlying function change and staleness propagation Apr 15, 2019
@Norbo11 Norbo11 added the enhancement Small feature or request label May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Small feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Norbo11