This repository was archived by the owner on Aug 14, 2019. It is now read-only.
updates %behn to no-op if its unix-duct is unset #1130
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
Various vanes set timers during the boot sequence, and
%behnimmediately gives%dozeeffects as appropriate. This combination was requiring that the%bornevent (new process notification) be injected as early as possible, and generally made %behn inflexible during boot.I can't think of any reason why it might be harmful to defer the
%dozeeffect -- any pending timers will be picked up and processed as soon as the%bornevent is injected.