1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
//! [`Optimizer`] trait + [`LearningRate`] schedule wrapper.
//!
//! Ports the base interface of Python `mlx.optimizers.Optimizer`
//! (`mlx/python/mlx/optimizers/optimizers.py:10..=155`) +
//! the Swift `Optimizer` protocol +
//! `OptimizerBase` /
//! `OptimizerBaseArrayState`
//! (`mlx-swift/Source/MLXOptimizers/Optimizers.swift:1..=100`).
//!
//! Python keeps optimizer state in a nested `dict` walked in lock-step with
//! the parameter tree via `tree_map`. mlxrs flattens this to a `HashMap<String,
//! Array>` (or `HashMap<String, (Array, Array)>` for two-moment families) —
//! see the [module-level deviation note](super#trait-shape-deviation-from-python).
//!
//! ## Learning-rate schedules
//!
//! Each optimizer takes a [`LearningRate`] at construction time. This is
//! either a `LearningRate::Fixed(f32)` (Python `float`) or a
//! `LearningRate::Schedule(Box<dyn Fn(usize) -> f32>)` (Python
//! `Callable[[step], float]`) — mirroring the Python `Union[float,
//! Callable]` pattern. The optimizer queries the schedule via
//! [`LearningRate::try_current`] in [`Optimizer::preflight`], caching the
//! result with a step stamp so the schedule closure is called at most ONCE
//! per step (resolve-once guarantee, issue #244).
use crate::;
/// Learning-rate value or step-driven schedule.
///
/// Mirrors Python's `Union[float, Callable[[mx.array], mx.array]]`
/// argument shape on every optimizer's `learning_rate` parameter
/// (`optimizers.py:230..=254`, `297..=325`, etc.).
/// Common interface for all gradient-descent optimizers.
///
/// Mirrors Python `mlx.optimizers.Optimizer`
/// (`mlx/python/mlx/optimizers/optimizers.py:10..=155`) +
/// the Swift `Optimizer` protocol
/// (`mlx-swift/Source/MLXOptimizers/Optimizers.swift:12..=16`).
///
/// ## Lifecycle
///
/// 1. Construct (`Type::new(...)` per optimizer).
/// 2. Optional: call [`Optimizer::init`] with the parameter tree to pre-
/// populate state (Python `optimizer.init(params)`). If skipped, the
/// first [`Optimizer::apply_gradients`] call auto-inits.
/// 3. Each training step: build `gradients` (e.g. via
/// [`crate::transforms::value_and_grad`]), call
/// [`Optimizer::apply_gradients`] with `gradients` + `params`. The
/// optimizer mutates `params` in-place with the updated weights and
/// advances its internal step counter.
/// Helper: build a `HashMap<String, Array>` of zero-filled state tensors,
/// one per param entry, with the same shape and dtype as each parameter.
///
/// Mirrors the Python `init_single` recipes that all do
/// `state["v"] = mx.zeros_like(parameter)`. Centralized so each optimizer's
/// `init` stays a one-liner.
pub
/// Build a fresh zero-filled `Array` with the same shape and dtype as
/// `template`. Re-export of [`crate::ops::misc::zeros_like`].
pub