add argument to explicitly disable buffer aliasing #10
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
|
yeah, it should probably wait |
|
I think this should be merged now that 3.11 is out :) |
|
should be change to true/false |
dyfer
force-pushed
the
disable-buffer-aliasing
branch
from
b700077 to
fbe10ab
Compare
dyfer
force-pushed
the
disable-buffer-aliasing
branch
from
fbe10ab to
8b4a63f
Compare
|
done! |
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.
Now that supercollider/supercollider#4356 is in, this can be added to the examples.
However, should we wait till 3.11 to merge this?