[PATCH] D109871: [flang][docs] Document plugin limitations

[Andrzej Warzynski via Phabricator via llvm-commits]

awarzynski added a comment.

@kiranchandramohan, thank you the suggestion!

In D109871#3003369 <https://reviews.llvm.org/D109871#3003369>, @kiranchandramohan wrote:

> I have a suggestion.
>
> Note that we intend to replace the traversal API with an API based on function object style.

I wouldn't add this here. It's something that we would like to happen, but AFAIK it's not being worked on actively. Also, I would prefer for this document to focus on the currently available interface. We know that it works fine as there are tests to defend that.

> Plugin writers should therefore not expect these classes to be stable and keep in mind the need for maintenance.

I don't think that we need this. AFAIK, there are no guarantees about the stability of any of the C++ APIs within llvm-project. LLVM only mentions the stability of the C API <https://llvm.org/docs/DeveloperPolicy.html#c-api-changes>. Sadly, we are unable to make any guarantees to to our downstream users, regardless of whether it's for plugins or other libraries within LLVM Flang.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D109871/new/

https://reviews.llvm.org/D109871