it should be straightforward, just remove the fina...

# arrow

[pakoito]

it should be straightforward, just remove the final property from fields here: https://bit.ly/2LozIWO

[Ryan Benasutti]

I agree with Henry here,

it seems likely that it should avoid writing to synthetic fields (and probably also final static ones).

Why does Arrow need to write to final fields?

[pakoito]

to be able to use coroutines for multi-shot constructs like monads we have to copy over all the coroutine state and just reset the stack label

[pakoito]

we asked for an API to do it cleanly, didn’t get it on time, so this is what’s working ever since the first release

[Ryan Benasutti]

Ok, I will give it a try. Hopefully it does not break pitest

[Ryan Benasutti]

How should I build a snapshot for myself to test with? (I don't see a publishToMavenLocal)

[pakoito]

https://jitpack.io/#arrow-kt/arrow

[pakoito]

I’d suggest forking arrow, copying the offending project somewhere in a test module

[pakoito]

and using a local version of the project

[Ryan Benasutti]

I'm struggling to get a build, do you think you could throw a patch together and send me a build I can test with? I'm not entirely sure this is right, but the fix should be something like adding this under it.isAccessible = true :

it.setInt(it, it.modifiers.and(Modifier.FINAL.inv()))