You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
auto rows = client.option_history_greeks_eod("SPY", "20230120", "0", "C", "20221219", "20221220", options);
89
89
```
@@ -218,7 +218,13 @@ The official streaming API exposes `STREAM` requests with `sec_type: "INDEX"` an
218
218
219
219
## Rust Builder vs Fixed-Arity Bindings
220
220
221
-
Rust is the closest direct projection of the merged current REST routes because optional query parameters stay on builder methods.
221
+
Rust is the closest direct projection of the merged current REST routes because required parameters stay in the constructor call and optional query parameters stay on builder methods. That chained style is intentional, not a special case for `strike_range`.
222
+
223
+
Other SDKs project the same optional surface idiomatically for their language:
224
+
225
+
- Python uses keyword-only optional parameters
226
+
- Go uses `WithOptions` helpers plus `EndpointRequestOptions`
227
+
- C++ uses `EndpointRequestOptions` overloads
222
228
223
229
Example:
224
230
@@ -237,7 +243,7 @@ Python, Go, and C++ still expose fixed-arity convenience methods for the common
237
243
238
244
- exact single-date helper when the binding exposes it
239
245
- dedicated range helper when the binding exposes it, such as `stock_history_ohlc_range`
240
-
- Python keyword-only optional parameters, Go `WithOptions` helpers, or C++ `OptionRequestOptions` overloads when the binding exposes them
246
+
- Python keyword-only optional parameters, Go `WithOptions` helpers, or C++ `EndpointRequestOptions` overloads when the binding exposes them
241
247
- Rust for the most faithful 1:1 projection of the official optional query surface
0 commit comments