This is an archive of the discontinued LLVM Phabricator instance.

[NFC] Fix typos in Clangd and Clang
ClosedPublic

Authored by kbobyrev on Dec 13 2019, 1:26 AM.

Diff Detail

Event Timeline

kbobyrev created this revision.Dec 13 2019, 1:26 AM
Jim accepted this revision.Dec 15 2019, 6:42 PM
This revision is now accepted and ready to land.Dec 15 2019, 6:42 PM
kbobyrev updated this revision to Diff 234001.Dec 16 2019, 1:30 AM

Rebase on top of master, fix the build and apply formatting.

This revision was automatically updated to reflect the committed changes.
Herald added a project: Restricted Project. · View Herald TranscriptDec 16 2019, 1:55 AM

Renaming handleDeclOccurence, handleMacroOccurence and handleModuleOccurence are definitely not NFC because they are public APIs that can be used by downstream projects.

Renaming handleDeclOccurence, handleMacroOccurence and handleModuleOccurence are definitely not NFC because they are public APIs that can be used by downstream projects.

I'm sorry if it broke some donwstream buildbots for the projects. I thought NFC is something that does not change behavior of the code (which is the case in this patch?) so is there something else that can make a patch NFC?

Also, if there is anything I could help with (e.g. submitting patches to some projects you know are affected by this change) please let me know.

In addition to that, NFC is also often used as a way to tag commits that should not cause any problems.
wrt to this change, I don't think anything was done wrong. It even went through review, although often we don't send reviews for NFC changes.

Downstream projects should be ready to update their code when public API changes like this happen, LLVM does not promise to keep a stable public interface in the C++ APIs.