[KTIJ-38341]: Mark functional interface argument contexts as blocking - #3573
Open
Kirill Shulzhenko (kshulzh) wants to merge 1 commit into
Open
[KTIJ-38341]: Mark functional interface argument contexts as blocking#3573Kirill Shulzhenko (kshulzh) wants to merge 1 commit into
Kirill Shulzhenko (kshulzh) wants to merge 1 commit into
Conversation
Bart van Helvert (BartvHelvert)
added
the
Kotlin
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
https://youtrack.jetbrains.com/issue/KTIJ-38341/False-positive-Possibly-blocking-call-in-non-blocking-context-could-lead-to-thread-starvation
Here I added FunctionalInterface lambdas inspection support
I have a question about the full blocking/nonblocking inspection. It looks like inline functions are analyzed incorrectly. In the following example, the Thread.sleep call inside the inline run block is not highlighted, while the subsequent Thread.sleep call is