William Moses

bumping here @avik-pal

bump @avik-pal

bump @avik-pal

Looks like activity analysis cannot get the right answer statically. If you use `Enzyme.API.runtimeActivity!(true)` before running it fixes it, but let's leave this open so I can try to update...

As this now successfully throws a runtime activity error, am going to close (and it succeeds with runtime activity)

Regarding performance, two thngs to look for: 1) type instabilities. Anything come via @code_warntype or similar ? 2) if you add Enzyme.API.printperf!(true) it will show some performance warnings.

@MilesCranmer is this issue still live?

As this now successfully throws a runtime activity error, am going to close (and it succeeds with runtime activity)

cc @sethaxen so runtime activity does come with a significant sharp edge -- which I think is causing the test to fail. Specifically from the docs on runtime activity: ```...

A constant return generally is permitted, the issue here is when turning a constant input into a duplicated return.