Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Experiment in lock-free module invalidation #9639
Experiment in lock-free module invalidation #9639
Changes from 5 commits
0110d86
65e901b
bd590ca
655d9aa
a65178d
641d968
2d662fd
6348cf4
e6b6cf2
99d6560
7881f9d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code is now rewritten into a new
ModuleIndexing
Scala class that usesConcurrentHashMap
. Good encapsulation, but I still miss the answer to the fundamental question: What is the invariant to be consistent with?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem I see continues to be the same. Line 44 deals with
state.suggestions
and line 64 does that as well. But meanwhile anything can happen. What if a new request tomarkAsNotIndexed
comes in another thread?My experience with Enso code base and its readiness for concurrent execution doesn't support claims that advocate reason and/or logic. Even if they were present, it is questionable they were used in a sound way. Except using the most advanced concurrent building blocks, I only see attempts to avoid answers to the basic question: how that is supposed to work at all?