rewrite make_zero! and remake_zero! with ntuple over fields

[vchuravy]

No description provided.

[github-actions]

Benchmark Results

	main	d4f6bf6...	main / d4f6bf6...
basics/make_zero/namedtuple	0.0511 ± 0.0013 μs	0.0508 ± 0.0022 μs	1.01 ± 0.051
basics/make_zero/struct	0.264 ± 0.0059 μs	0.253 ± 0.0054 μs	1.04 ± 0.032
basics/overhead	5.26 ± 0.92 ns	4.34 ± 0.01 ns	1.21 ± 0.21
basics/remake_zero!/namedtuple	0.299 ± 0.0065 μs	0.234 ± 0.0042 μs	1.28 ± 0.036
basics/remake_zero!/struct	0.307 ± 0.0076 μs	0.233 ± 0.0034 μs	1.32 ± 0.038
time_to_load	1.27 ± 0.008 s	1.27 ± 0.0086 s	1 ± 0.0092

Benchmark Plots

A plot of the benchmark results has been uploaded as an artifact at https://github.com/EnzymeAD/Enzyme.jl/actions/runs/18039430455/artifacts/4115489625.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.30%. Comparing base (8da98df) to head (d4f6bf6).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2607   +/-   ##
=======================================
  Coverage   75.30%   75.30%           
=======================================
  Files          57       57           
  Lines       17751    17751           
=======================================
  Hits        13368    13368           
  Misses       4383     4383           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[wsmoses]

honestly this feels like it should become a generated function (and we can also therefore conditionally create the seen dict if there is > 1 potentially aliasing piece of data)

[vchuravy]

ntuple is a generated function, just one that is limited in scope. I still prefer this over the headache that generated function bring with them otherwise.

I also don't think it would be unreasonable for a user to provide their own make_zero function / remake_zero! function.

[wsmoses]

yeah we definitely want user definable overrides. I'm just dreaming of a world where we don't need the explicit specialization for make_zero(Array) in addition to make_zero(Array, seen).

in any case we can figure this out later, this is already clearly a good change

[vchuravy]

Also sadly while we might be able to use a generated function, that would only allow us to guard against recursion in the type-domain and not recursion in the value domain :/

[wsmoses]

Perhaps but things like make_zero of a tuple of floats is sufficiently common that we really want it to use the right thing without the is check