Btw why did you wrap my compile-testing library? I...

# arrow-meta

[tschuchort]

Btw why did you wrap my compile-testing library? Is the API not good enough?

[raulraja]

The API is great but we want meta users to use the same style they use in quotes, codegen, ide and tests

[raulraja]

additionally we need to add to the DSL the quote system which is a compiler phase

[raulraja]

basically inline plugins that are written in the tests

[raulraja]

and we are trying to figure that out

[raulraja]

you are welcome to suggest improvements, the only issues we had with your lib so far is that we had no version to rely on so we had to use a jitpack fork

[tschuchort]

What do you mean with same style? If any improvements can be upstreamed I definitely want to do so, so that everyone can benefit from them.

[tschuchort]

For inline plugins you need the PR for better compiler plugin support, which is practically finished except for finding out the kapt-initialization order. We need to know if third-party compiler plugins are run before or after kapt stubs generation (or maybe not at all in the kapt-step). If you could find that out it would be a big help and I could merge&release it immediately. Should be enough to add some dummy method to classes in a compiler plugin and then observe in an annotation processor if it appears or not.

[Rachel]

Hi @tschuchort, thanks for your help! I made a drawing to tell what we did:

https://user-images.githubusercontent.com/22792183/68107674-e4235f00-fee5-11e9-8848-e53f14cfeee6.jpg▾

[Rachel]

In this way, tests can be written like this one: https://github.com/arrow-kt/arrow-meta/blob/master/compiler-plugin/src/test/kotlin/arrow/meta/plugins/lens/LensTest.kt