LDC 0.16.0 removed the -noboundschecks flag, replace with -boundscheck=off #693
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
…k=off which is already existing in 0.15.x
MartinNowak
added a commit
that referenced
this pull request
Sep 22, 2015
LDC 0.16.0 removed the -noboundschecks flag, replace with -boundscheck=off
|
Did they remove it immediately, or has there been a transition phase? If not, we might need to make this dependent on the compiler version. |
|
@s-ludwig I think 0.15.x was the transition phase, since this version has both flags. |
|
Okay, I guess that's acceptable then. |
|
Is there any chance of getting a new dub release soon including this fix? Currently Travis CI doesn't work out of the box with 0.16.x LDC because it uses the latest release (0.9.24) which uses the old flag. |
|
We might want to support it in DMD as well, as this switch appeared in 2.066: http://dlang.org/changelog/2.066.0.html |
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.
This flag is already existing in 0.15.x so it breaks nothing.