Ported fix for premature CB initalisation #74
Merged
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
yassiezar
force-pushed
the
fix-premature-cb-init
branch
from
15e4310 to
64196fb
Compare
yassiezar
force-pushed
the
fix-premature-cb-init
branch
from
64196fb to
27eb026
Compare
|
This is a great contribution because fix a know bug in smacc2 that was already fixed, but that was not synchronized in smacc1. |
pabloinigoblasco
approved these changes
Dec 1, 2022
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.
Porting over premature initialisation guard from #61
┆Issue is synchronized with this Jira Task by Unito