Dumb question: Is it possible to run `Arrow-Analysis` in a separate compilation task from regular? ...

# arrow

[Gavin Ray]

Dumb question: Is it possible to run Arrow-Analysis in a separate compilation task from regular?

The reason I ask is because of potentially increased compile times, which I assume would add up if you're frequently re-compiling your code to test. (Maybe this is not the case though)

[Alejandro Serrano Mena]

unfortunately the analysis has to run alongside compilation, due to how we’ve implemented it

[Alejandro Serrano Mena]

maybe it’s possible to create separate tasks for “compile without the plugin” and “compile with the plugin” @raulraja do you happen to know about that?

[raulraja]

yes, we could provide in the gradle plugin a task or plugin parameter that does not registrer our extensions or tells the gradle plugin for that run it should skip analysis.

[raulraja]

I would make this opt-in, being the default behaviour that analysis runs with the regular build.

[raulraja]

@Gavin Ray would that cover your use case?

[Gavin Ray]

That would be amazing, thank you!

[raulraja]

@Gavin Ray if you want to create an issue with your use case we will go over it and triage it in our next maintainers meeting https://github.com/arrow-kt/arrow-meta/issues