[DO NOT MERGE] updated clang to v11.0.0 #89
Closed
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.
Similar to the one filed for cuML here: rapidsai/cuml#3121, this PR tries to show the set of changes especially with clang-format, after updating clang to 11.0.0. As can be seen from the diff's, there's almost no change in clang-format fixes by upgrading to 11.0.0 from 8.0.1. So, it should be safe to update clang version in our conda env's in RAPIDS to 11.0.0.