Comments for target and source sites of async scheduling #6780
Conversation
This file contains 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
…a delay()/esp_yield()/esp_schedule()
d-a-v
approved these changes
Nov 15, 2019
|
@d-a-v oh great, thanks, that makes it much easier presenting a fix/change to the code spots. PR coming right next. Thanks again :-) |
|
Continued in #6782 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Where async event scheduling uses
delay()/esp_yield()andesp_schedule(), use same wording and properly identify source / target site pairs.This is a purely cosmetic PR.
This PR helps identify these sites and aids in (my) discussion about the effects this pattern has on the
compatibility to (AVR) Arduino-style overridable weak-binding yield()/__yield() based 3rd party scheduling libraries.