Remove and ignore .clangd file.

[bdice]

Description

This PR removes an extraneous .clangd configuration that was added during the devcontainers PR #1328. This file was not committed to any other RAPIDS repos with devcontainers and is listed in .gitignore for several RAPIDS repos, so it's safe to remove. I also added an ignore for .nfs* to match cudf's ignore list -- this is helpful when network file systems create temporary cruft.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[harrism]

I rely on clangd. Is this change going to break it?

[bdice]

I rely on clangd. Is this change going to break it?

I don’t think so. This file seems to be autogenerated by rapids-compose (and devcontainers?), because I keep getting a diff locally in this file and have to ignore it every time I work on rmm. It is ignored by other repos that have devcontainers enabled and they seem to have clangd working fine.

[bdice]

Hmm. This PR might not be right. Other repos do have a cpp/.clangd file committed but have a gitignore entry for .clangd (presumably ignoring .clangd in the root). Maybe that file does need to be committed, but rmm is a special case because it doesn't have a cpp/ folder? @trxcllnt Do you have insight here?

[vyasr]

I've observed similar behavior in multiple repos where the clangd file is committed but is modified by something in compose.

[harrism]

@bdice indeed it seems that in dev containers there is an included feature that adds a clangd config in /home/coder/.config/clangd/config.yaml. I think this may be the source.

Hmm, here's another one.

The contents are mostly the same as, but slightly different from the .clangd this PR aims to remove.

[bdice]

From conversation with @trxcllnt, I think removing this file is probably wrong and will break clangd support in devcontainers. I'll close this PR.