pineforge-codegen 1.3.0__tar.gz → 1.5.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/CHANGELOG.md +317 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/PKG-INFO +145 -34
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/README.md +144 -33
- pineforge_codegen-1.5.0/VERSION +1 -0
- pineforge_codegen-1.5.0/docs/PUBLIC_CONTRACT.md +695 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/docs/pine-cap-activation.md +11 -6
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/__init__.py +66 -9
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/analyzer/base.py +3 -3
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/analyzer/types.py +7 -3
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/base.py +26 -16
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/checked_settings.py +113 -2
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/collection_history.py +163 -12
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/emit_top.py +24 -8
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/helpers.py +19 -1
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/host_members.py +1 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/input.py +23 -8
- pineforge_codegen-1.5.0/pineforge_codegen/codegen/run_stops.py +52 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/security.py +12 -5
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/tables.py +132 -28
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/tv_number_format.py +9 -2
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/types.py +85 -4
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/visit_call.py +174 -55
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/visit_expr.py +32 -6
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/visit_stmt.py +3 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/collection_history.py +122 -20
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/diagnostic_codes.py +18 -8
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/diagnostics_catalog.json +629 -628
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/errors.py +12 -1
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/external_requests.py +30 -9
- pineforge_codegen-1.5.0/pineforge_codegen/matrix_overloads.py +7 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/parser.py +7 -2
- pineforge_codegen-1.5.0/pineforge_codegen/request_feed_inventory.py +311 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/signatures.py +2 -2
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/support_checker.py +97 -6
- pineforge_codegen-1.5.0/pineforge_codegen/timeframe_token_cli.py +133 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pyproject.toml +1 -1
- pineforge_codegen-1.3.0/VERSION +0 -1
- pineforge_codegen-1.3.0/docs/PUBLIC_CONTRACT.md +0 -372
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/.gitignore +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/CONTRIBUTING.md +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/LEGAL.md +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/LICENSE +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/docs/codegen-coverage-gaps.md +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/analyzer/__init__.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/analyzer/call_handlers.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/analyzer/contracts.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/analyzer/diagnostics.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/analyzer/tables.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/ast_nodes.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/block_locals.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/builtin_keywords.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/__init__.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/capabilities.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/constant_fold.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/drawing.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/helpers_syminfo.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/order_shapes.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/session_market.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/codegen/ta.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/finite_ta_length.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/lexer.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/library_inline.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/library_modules.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/library_v5.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/limits.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/method_binding.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/pine_libraries.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/pine_spelling.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/pragmas.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/request_discovery.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/security_contexts.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/session_reads.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/symbols.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/tokens.py +0 -0
- {pineforge_codegen-1.3.0 → pineforge_codegen-1.5.0}/pineforge_codegen/tv_input_choices.py +0 -0
|
@@ -20,6 +20,323 @@ supported as exact pairs; on the 0.x line they are independent. See the
|
|
|
20
20
|
the release commit. A prerelease note describes changes since the preceding
|
|
21
21
|
prerelease or stable tag; the final stable note consolidates the series.
|
|
22
22
|
|
|
23
|
+
## 1.5.0 — 2026-10-12
|
|
24
|
+
|
|
25
|
+
A minor release of the exact engine/codegen pair, paired with engine `v1.5.0`
|
|
26
|
+
and dated 2026-10-12. This entry records the diagnostic additions below and the
|
|
27
|
+
report-contract documentation for the paired engine fix, and nothing else: the
|
|
28
|
+
codegen change is diagnostics only; the report documentation adds no Python,
|
|
29
|
+
JSON, diagnostic or emitted-C++ change of its own, and no analyzer or
|
|
30
|
+
code-generation file differs.
|
|
31
|
+
|
|
32
|
+
### Compatibility and migration
|
|
33
|
+
|
|
34
|
+
- **`note` is a third diagnostic severity, and it is nonfatal.** A diagnostic
|
|
35
|
+
is now an `error`, a `warning` or a `note`: `Level.NOTE` in Python and `"note"`
|
|
36
|
+
as the `severity` of a catalog entry and of a JSON diagnostic. A note is
|
|
37
|
+
nonfatal like a warning. `transpile_full()["diagnostics"]` and the success
|
|
38
|
+
envelope's `diagnostics` list warnings and notes, a script with only notes
|
|
39
|
+
still returns `ok: true` and its C++, and a `CompileError` can carry notes
|
|
40
|
+
beside its errors. `transpile()` still returns no nonfatal diagnostics.
|
|
41
|
+
`CompileError.format()` prints `note[...]` where it printed `warning[...]` for
|
|
42
|
+
the codes below. Code written for two severities must handle `note`: read an
|
|
43
|
+
unknown severity as a warning, never as an error. A note does not mean that
|
|
44
|
+
results are unaffected; PF-W1505 describes a warmup approximation.
|
|
45
|
+
- **Exactly eleven codes change from warning to note:** PF-W1505, PF-W1508,
|
|
46
|
+
PF-W1509, PF-W1525, PF-W1526, PF-W1527, PF-W1528, PF-W1529, PF-W1530,
|
|
47
|
+
PF-W1531 and PF-W1532. They describe calls PineForge skips as visual only
|
|
48
|
+
(`plot(...)`, `table.new(...)`), earnings, dividends, splits, financial,
|
|
49
|
+
footprint and other-symbol requests whose value reaches only display and alert
|
|
50
|
+
sinks and is lowered to `na`, and the `ta.ema` warmup approximation. Every
|
|
51
|
+
other code keeps its severity. PF-W1502 (`color(...)` cast), PF-W1506
|
|
52
|
+
(`color.from_gradient`), PF-W1507 (drawing setters that drop color, style or
|
|
53
|
+
size), PF-W1078 (visual or style constants) and PF-W1552 (a
|
|
54
|
+
`request.security_lower_tf` whose value reaches only display and alert sinks)
|
|
55
|
+
also speak of visual-only or display-only handling and remain warnings: a
|
|
56
|
+
message's wording does not classify it. A consumer that tallied these eleven
|
|
57
|
+
codes as warnings, to gate a run, count warnings or color a banner, now
|
|
58
|
+
receives notes. PF-W1509 still classifies as PF-W1508 where the two templates
|
|
59
|
+
tie, so no new emitted code appears.
|
|
60
|
+
- **`user_message` is a raw ICU template over `args`.** Every catalog entry,
|
|
61
|
+
every `Diagnostic` (`Diagnostic.user_message`) and every JSON diagnostic gains
|
|
62
|
+
`user_message`: a short English ICU template that uses only that diagnostic's
|
|
63
|
+
existing `args` names and may be constant (`{name}() does nothing in a backtest.`
|
|
64
|
+
with `args.name = "plot"`). It is not pre-rendered English. Render it with
|
|
65
|
+
`args` as plain text, never as template syntax or markup, or translate by
|
|
66
|
+
`code`; do not display the unrendered template. It does not replace `message`
|
|
67
|
+
and `hint`. The templates of the eleven migrated codes are fixed string for
|
|
68
|
+
string by a delta fixture. Every template is checked for form (short,
|
|
69
|
+
parseable, over that code's own `args` names). Each of the 97 warning twins
|
|
70
|
+
of an error (`PF-W1nnn` for `PF-E1nnn`) has a sentence of its own that says
|
|
71
|
+
PineForge warns, and the 91 that warn only inside a `switch` arm also say it
|
|
72
|
+
keeps the arm's lowering. No warning or note template says that PineForge
|
|
73
|
+
refuses or rejects something, though one may say what TradingView refuses or
|
|
74
|
+
rejects. Beyond these checks a template's exact wording is not pinned.
|
|
75
|
+
- **Legacy fields are stable.** `code`, `args`, `message`, `hint`, `line`,
|
|
76
|
+
`col`, `endCol`, `ok`, `error` and the envelope keys keep their meaning and
|
|
77
|
+
values: no key is renamed or removed, and no code is renumbered or reused (the
|
|
78
|
+
notes keep their `PF-W` codes, and the prefix is not the severity).
|
|
79
|
+
`render_diagnostic()` still returns the unchanged English `message` and
|
|
80
|
+
`hint`. The catalog schema id stays `pineforge-diagnostics-catalog/v1`, so a
|
|
81
|
+
reader that checks `severity` against two values or rejects unknown entry
|
|
82
|
+
fields must accept `note` and `user_message`. The receiver examples in
|
|
83
|
+
`tests/fixtures/diagnostic_notes/receiver.json` specify the compatibility
|
|
84
|
+
rule; they are not evidence of any application's behavior.
|
|
85
|
+
- **The warmup sidecar is later work.** No compile-time or runtime sidecar
|
|
86
|
+
exists in this entry. PF-W1505 stays the static `ta.ema` note it was, with
|
|
87
|
+
only its severity changed: the support checker emits it at each `ta.ema` call
|
|
88
|
+
it visits, with no per-call condition or suppression and no call-site
|
|
89
|
+
identifier. The startup inventory and extraction that would bind a versioned
|
|
90
|
+
sidecar to a diagnostic by `call_site_id` and source range, so that a consumer
|
|
91
|
+
can show a startup sentence only for a known finite shortfall, are not part of
|
|
92
|
+
this entry, and no diagnostic carries a call-site identifier or a startup
|
|
93
|
+
length.
|
|
94
|
+
|
|
95
|
+
### Documentation
|
|
96
|
+
|
|
97
|
+
The engine side of the report-ownership text below is a report fix, in
|
|
98
|
+
preparation, that engine `v1.4.0` does not carry.
|
|
99
|
+
|
|
100
|
+
- The [public contract](docs/PUBLIC_CONTRACT.md#a-report-belongs-to-the-call-that-returned-it)
|
|
101
|
+
states that a report belongs to the call that returned it. A call the engine
|
|
102
|
+
refuses without beginning gets the empty report, never an earlier run's rows;
|
|
103
|
+
a run that began and then failed keeps its partial rows; the explicit stream
|
|
104
|
+
snapshot keeps the owner's rows; recorded outputs keep their own record of
|
|
105
|
+
the last run that began.
|
|
106
|
+
- Read the error text, the error code **and** the run status after every run.
|
|
107
|
+
A refusal the engine makes before it admits the begin leaves the status at its
|
|
108
|
+
earlier value (0 after a completed run), so the status alone misses it. The
|
|
109
|
+
README's "Compile & run against the engine" section says the same.
|
|
110
|
+
- Pairing is unchanged in kind: regenerate the strategy C++ and relink against
|
|
111
|
+
the engine release's headers and `libpineforge.a` on a pair change (README
|
|
112
|
+
[Engine pairing](README.md#engine-pairing)).
|
|
113
|
+
|
|
114
|
+
## 1.4.0 — 2026-10-08
|
|
115
|
+
|
|
116
|
+
A minor release of the exact engine/codegen pair. Its behavior was validated
|
|
117
|
+
before tagging on codegen `bfc4ddce` and engine `b3192bfc`.
|
|
118
|
+
It consolidates the seven requests landed
|
|
119
|
+
since `v1.3.0`: [#183](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/183)
|
|
120
|
+
(emission ordering), [#184](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/184)
|
|
121
|
+
(coded run stops), [#185](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/185)
|
|
122
|
+
(input manifests), [#186](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/186)
|
|
123
|
+
(collection history and binding), [#188](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/188)
|
|
124
|
+
(CI history), [#189](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/189)
|
|
125
|
+
(reference tests), and [#190](https://github.com/pineforge-4pass/pineforge-codegen-oss/pull/190)
|
|
126
|
+
(emitted-string regressions and edge cases). Recorded-output support from
|
|
127
|
+
engine request #356 is excluded. The pre-tag validation used these commits
|
|
128
|
+
with `VERSION` equal to `1.3.0`; those results are not post-tag measurements.
|
|
129
|
+
|
|
130
|
+
### Compatibility and migration
|
|
131
|
+
|
|
132
|
+
- Codegen 1.4.0 supports only engine `v1.4.0`. Regenerate every strategy's C++
|
|
133
|
+
and relink with that release's generated headers and `libpineforge.a`.
|
|
134
|
+
The pair retains C ABI version 4, settings/capability API version 1 and the
|
|
135
|
+
`engine_script_run_v19` epoch; equal version numbers for those interfaces
|
|
136
|
+
do not make mixed engine/codegen releases supported.
|
|
137
|
+
A report's fingerprint records engine/codegen versions, generated C++'s
|
|
138
|
+
hash and the paired engine's corrected provenance values. The retained
|
|
139
|
+
epoch and hash domain tags do not promise equal fingerprints, state-hash
|
|
140
|
+
values or trades across 1.3.0 and 1.4.0.
|
|
141
|
+
- Emitted C++ changes, including common run-stop shims and collection history
|
|
142
|
+
wrappers. Do not reuse a 1.3.0 strategy library or assume source identity.
|
|
143
|
+
The public Python call signatures and override keys stay the same, but
|
|
144
|
+
`inputs` values and the Python/Pyodide success envelopes change as described
|
|
145
|
+
below. These are not blanket byte-identity promises for emission or envelopes.
|
|
146
|
+
- Every manifest row now carries `supported`. When it is `false`, hide the
|
|
147
|
+
input, exclude it from sweeps and optimization, and do not send a value:
|
|
148
|
+
the strategy uses its compiled default, and the paired engine refuses a
|
|
149
|
+
supplied value with `setting_unsupported`. `supported: true` alone does
|
|
150
|
+
not validate the value's type, bounds or options, or make a shared key safe.
|
|
151
|
+
A supported empty dropdown and an unsupported string input can both have
|
|
152
|
+
`options: []`; that list does not determine support.
|
|
153
|
+
- Give each input a unique title before upgrading. Calls with the same title
|
|
154
|
+
or fallback declaration key still produce separate manifest rows with the
|
|
155
|
+
same `title`; their `supported` flags do not detect the collision. Different
|
|
156
|
+
`group=` labels do not separate keys. On the paired 1.4.0 engine's normal
|
|
157
|
+
checked path, a completed run of such a script has `fingerprint: null` even
|
|
158
|
+
without an override. Supplying the shared key fails before execution with
|
|
159
|
+
`setting_rejected`, reason `ambiguous_key`. For example,
|
|
160
|
+
`Period="7"` returned a success report on 1.3.0, whose legacy setter applied
|
|
161
|
+
a shared key to all matching inputs. Legacy-path unresolved provenance rows
|
|
162
|
+
may still appear inside a fingerprint; that differs from the whole
|
|
163
|
+
fingerprint being null on the checked path.
|
|
164
|
+
- The paired engine's run harness now uses the checked settings API. Stored
|
|
165
|
+
presets and sweep values must satisfy the compiled input's type, bounds and
|
|
166
|
+
options. Two other examples that succeeded on 1.3.0 now fail with
|
|
167
|
+
`setting_rejected`: `Color="color.blue"` (`expected_integer`) and
|
|
168
|
+
`Choice="15"` for options `[10, 20, 30]` (`invalid_input_option`). A color's
|
|
169
|
+
manifest still has `type: "string"` and a Pine spelling such as `"color.red"`
|
|
170
|
+
as its default, but the checked native input requires the packed integer;
|
|
171
|
+
do not forward that manifest string as a native color value. The checked
|
|
172
|
+
API also validates parseable numbers, booleans, enum members and known keys.
|
|
173
|
+
This does not mean all invalid settings previously succeeded:
|
|
174
|
+
`initial_capital="abc"` and `initial_capital="-1"` already failed on 1.3.0;
|
|
175
|
+
they now report `expected_finite_decimal` and `value_below_minimum` reasons.
|
|
176
|
+
Legacy C setters retain their existing behavior.
|
|
177
|
+
- The paired engine adds `strategy_get_last_error_code` and
|
|
178
|
+
`strategy_get_last_error_args` beside the existing English error getter,
|
|
179
|
+
under `PINEFORGE_HAS_RUN_FAILURE_CODES_V1`. Its run harness exposes `code`
|
|
180
|
+
and typed `args` beside `error` on failures. Check the failure channel even
|
|
181
|
+
when the English message is empty; do not accept a stopped run's partial
|
|
182
|
+
output as success or parse the English to recover a code. These run failures
|
|
183
|
+
are distinct from transpile-time `CompileError` diagnostics.
|
|
184
|
+
`setting_rejected` is catalog class `input`; `setting_unsupported` is class
|
|
185
|
+
`unsupported`. A deliberate `runtime.error` is `strategy_runtime_error`,
|
|
186
|
+
class `strategy`. The installed engine entrypoint returns exit 4 for all
|
|
187
|
+
three codes: exit 4 alone does not select a billing or refund decision.
|
|
188
|
+
- The paired engine certifies scalar input/override types in fingerprint
|
|
189
|
+
provenance; unresolved values remain explicit rather than being treated as
|
|
190
|
+
certified native values. This is an engine report change, not another field
|
|
191
|
+
added to the transpile-time input manifest. See the paired engine's release
|
|
192
|
+
notes for report resolution reasons and counts.
|
|
193
|
+
|
|
194
|
+
### Emission and run failures
|
|
195
|
+
|
|
196
|
+
- Requested-context history resets and TA variant position ties no longer
|
|
197
|
+
use address or set order; they preserve traversal order. Refusal
|
|
198
|
+
diagnostics for conflicting scalar history and map locals are hash-seed
|
|
199
|
+
independent.
|
|
200
|
+
- Generated run stops use stable engine failure codes when the paired engine
|
|
201
|
+
advertises `PINEFORGE_HAS_RUN_FAILURE_CODES_V1`. No-data and other-symbol
|
|
202
|
+
stops carry compile-time request provenance; copying their English into
|
|
203
|
+
`runtime.error` cannot select their codes. Older engines keep the legacy
|
|
204
|
+
throws and English messages.
|
|
205
|
+
- `runtime.error(message = "...")` now passes the named message. With the
|
|
206
|
+
coded engine and run harness, a run stopped by `runtime.error()` with an
|
|
207
|
+
empty or named message no longer reports success or exposes partial results.
|
|
208
|
+
- `str.tonumber` no longer hides a stop raised while evaluating its argument;
|
|
209
|
+
only numeric parse failures become `na`. Invalid array sizes, substring
|
|
210
|
+
positions and overflowing format-placeholder indices have checked stops.
|
|
211
|
+
String parsing and checked substring calls do not capture authored helper-like
|
|
212
|
+
names; substring arguments retain source order without copying the source text.
|
|
213
|
+
- Generated run wrappers preserve the inner failure code, and latched setter
|
|
214
|
+
failures and checked strategy construction retain their failure identity.
|
|
215
|
+
|
|
216
|
+
### Python and Pyodide input metadata
|
|
217
|
+
|
|
218
|
+
- The transpile-time input manifest (`transpile_full()["inputs"]` and the JSON
|
|
219
|
+
envelope of the Pyodide package) gains `supported`, the checked-settings
|
|
220
|
+
receipt's flag, on every input, and reads its defaults, choices and bounds
|
|
221
|
+
from the descriptor that generates the receipt, with the retained limitations
|
|
222
|
+
below. No manifest key is renamed or removed, but these values of existing
|
|
223
|
+
keys change:
|
|
224
|
+
- Source inputs (`input.source`, a plain `input(close)`): `default` is the
|
|
225
|
+
series name, where it was `null`, and `options` lists the nine native
|
|
226
|
+
sources, where it was absent.
|
|
227
|
+
- Enum inputs: `options` lists the `Enum.member` choices, where it was
|
|
228
|
+
absent; `default` keeps its `Enum.member` spelling. The compiled receipt
|
|
229
|
+
encodes that default as its integer member value.
|
|
230
|
+
- String inputs: a built-in constant publishes its runtime value
|
|
231
|
+
(`alert.freq_all` is `"all"`, `currency.USD` is `"USD"`; the manifest held
|
|
232
|
+
the Pine names), a named string constant its value, and the choices of
|
|
233
|
+
`input.timeframe` and `input.session` are listed. What the receipt cannot
|
|
234
|
+
represent (`size.small`, `position.top_right`, `na`) has `supported: false`
|
|
235
|
+
and `options: []`; an unavailable default is `""`, but a representable
|
|
236
|
+
default survives an unsupported choice. String decoding uses the emitter
|
|
237
|
+
escape grammar, keeps literal Unicode and escaped backslashes, and stops
|
|
238
|
+
at the first NUL like the receipt's `std::string(const char*)` constructor.
|
|
239
|
+
NUL is emitted as a fixed three-digit octal escape even before digits;
|
|
240
|
+
this is consistency with current native truncation, not lossless NUL storage.
|
|
241
|
+
- Typed `int`, `float`, `price` and `time` inputs: a signed or
|
|
242
|
+
named-constant `default` is a number, where it was `null`; `min`, `max` and
|
|
243
|
+
`step` appear for signed and named-constant bounds (`minval=-80` was left
|
|
244
|
+
out); an `options=[...]` dropdown lists its numbers. A literal or inlined
|
|
245
|
+
`bool` default publishes a boolean, not a number.
|
|
246
|
+
- A plain `input(-5)` or `input(-2.5)` is typed `int` or `float` with its
|
|
247
|
+
number as `default`, where it was `string` with `null`. The compiled
|
|
248
|
+
getter and checked receipt keep their existing float type for these
|
|
249
|
+
signed plain inputs; this manifest correction does not change that lowering.
|
|
250
|
+
|
|
251
|
+
Values the receipt computes at run time (`LEN * 2`, `not true`,
|
|
252
|
+
`timestamp(year, month, ...)`) stay unpublished: the default remains
|
|
253
|
+
`None`/JSON `null`, an unfoldable bound is omitted, and the whole `options`
|
|
254
|
+
field is omitted when any numeric choice is unfoldable. An `input.color`
|
|
255
|
+
retains its Pine spelling as a string default, not the receipt's packed
|
|
256
|
+
integer; other nonliteral plain `input()` calls remain `string` with no
|
|
257
|
+
published default (the source case above is the exception). A folded
|
|
258
|
+
`timestamp("...")` is a publishable literal. These gaps
|
|
259
|
+
are explicit in `tests/test_input_metadata_receipt.py::KNOWN_LIMITS`, not a
|
|
260
|
+
claim of arbitrary expression evaluation or language soundness.
|
|
261
|
+
- Documents the timeframe spellings of two surfaces, both stable: a capability
|
|
262
|
+
receipt records a request's timeframe as the script wrote it (`"D"`), and
|
|
263
|
+
request discovery and feed keys use the engine's spelling (`"1D"`).
|
|
264
|
+
|
|
265
|
+
### Collection lowering and refusals
|
|
266
|
+
|
|
267
|
+
- Bind keyword arguments of the matrix methods and the checked array methods to their own parameter slot, with the omitted optional parameters taking their defaults in place (`matrix.sort(m, order = order.descending)`, `m.submatrix(to_column = 1)`, `a.fill(7.0, index_to = 1)` no longer drop or shift a keyword), and refuse a keyword that names no parameter, or a parameter given twice, with the existing argument diagnostics. A defaulted `submatrix` evaluates its receiver once, an index-only `add_row` / `add_col` takes any numeric index, and a bound `array.concat` result (`c = a.concat(b)`, `c := array.concat(a, b)`) keeps the unsupported-function refusal. An array history that reaches a user function's or method's parameter keeps its earlier copy lowering and the earlier refusal of a callee that checks it with `na()`; a bound missing-history matrix reports the recorded na-ID runtime error.
|
|
268
|
+
- Compile matrix/matrix and matrix/scalar `matrix.sum` overloads with matrix-valued results, including helpers and history. Support scalar `matrix.diff`/`matrix.mult` and omitted optional arguments to matrix row/column insertion, submatrix, sort and array fill; unsupported matrix/vector multiplication and bound `array.concat` results report an existing unsupported-function diagnostic instead of failing C++ compilation.
|
|
269
|
+
- Preserve na array IDs when a history offset has no value, including aliases and `na()`-only bindings; array methods on those IDs report the existing runtime error instead of crashing. Bounds-check legacy collection-element reads and writes to prevent unchecked access.
|
|
270
|
+
|
|
271
|
+
The inherited follow-ups remain: keywords on UDT matrix fields, `matrix.new`
|
|
272
|
+
and array methods outside the checked table; `matrix.fill` range handling
|
|
273
|
+
(both spellings still fill the whole matrix); matrix diff/mult dimension
|
|
274
|
+
checks; and nullable history across callable/iteration shapes not covered by
|
|
275
|
+
the documented lowering. This release does not claim those cases resolved.
|
|
276
|
+
|
|
277
|
+
### Emitted-string edge cases and maintenance
|
|
278
|
+
|
|
279
|
+
- Return the prefix or ticker of the supplied symbol in `syminfo.prefix(symbol)`
|
|
280
|
+
and `syminfo.ticker(symbol)` instead of always reading the chart symbol; the
|
|
281
|
+
variable forms, no-argument calls and direct chart-ID calls keep their
|
|
282
|
+
chart lowering. Supplied-symbol calls split at the first colon; a prefix
|
|
283
|
+
is empty without a colon or with no ticker after it, and a ticker without
|
|
284
|
+
a colon is the full string. Non-string arguments still compile and yield
|
|
285
|
+
an empty string, including the retained string-`na` typing gap.
|
|
286
|
+
- Refuse malformed library versions with the existing import diagnostic instead
|
|
287
|
+
of allowing them to raise outside the JSON gate, including non-ASCII decimal
|
|
288
|
+
digits and ASCII versions exceeding Python's integer-conversion limit.
|
|
289
|
+
- Reserve generated receipt exports and version macros against script names.
|
|
290
|
+
- Escape embedded NUL values in generated C++ string literals, and strengthen
|
|
291
|
+
emitted-string regression tests with explicit emitter reach and round trips.
|
|
292
|
+
- CI fetches full branch history for historical reference tests (#188); two
|
|
293
|
+
whole-C++ comparisons use the accepted immutable scaffold (#189). These
|
|
294
|
+
changes affect verification only, not the compiler or execution semantics.
|
|
295
|
+
|
|
296
|
+
The hardening wording remains scoped to the previously documented emitted-string
|
|
297
|
+
validation and escaping; these edge-case repairs and regression checks are not
|
|
298
|
+
a new arbitrary-source security guarantee. No exploit payloads are included.
|
|
299
|
+
|
|
300
|
+
### Known issues with consumers
|
|
301
|
+
|
|
302
|
+
The new numeric options expose an exact-type comparison in
|
|
303
|
+
`pineforge-hpo` 0.11.0: a JSON integer `20` is refused with
|
|
304
|
+
`invalid_input_option` for an `input.float` choice `20.0`, although the
|
|
305
|
+
numbers are equal. For HPO 0.11.0, send each selected value with the number
|
|
306
|
+
type the original manifest publishes for that option: `20.0` when it lists
|
|
307
|
+
`20.0` (explicit JSON `20.0` or a Python float), and integer `20` when it lists
|
|
308
|
+
`20`. A float input written with whole-number-literal options such as
|
|
309
|
+
`options=[10, 20, 30]` publishes integer options; mixed lists retain mixed
|
|
310
|
+
number types. The input's `float` type alone does not choose the workaround.
|
|
311
|
+
|
|
312
|
+
This can affect a caller that reads a float-spelled manifest default and
|
|
313
|
+
sends it back through JavaScript's ordinary JSON serialization, which writes
|
|
314
|
+
a whole-number value as `20`, losing its float spelling. Writing `20.0` in
|
|
315
|
+
JavaScript before ordinary serialization does not preserve that distinction;
|
|
316
|
+
preserve each option's original number type at the HPO boundary. Upgrade to
|
|
317
|
+
HPO 0.11.1 or a later release containing the fix when available. This fix is
|
|
318
|
+
separate from the engine/codegen release; HPO 0.11.1 has not been released at
|
|
319
|
+
the time of writing.
|
|
320
|
+
|
|
321
|
+
### Recorded validation and grades
|
|
322
|
+
|
|
323
|
+
The landed #190 candidate recorded 9,254 engine-enabled pytest passes with
|
|
324
|
+
12 audited skips, 2,164 focused passes each under GCC and Clang without skips,
|
|
325
|
+
314 public corpus compilation passes, and 279 fixtures in each of the JSON
|
|
326
|
+
and Pyodide fixture-parity checks. Those
|
|
327
|
+
are the request's retained native measurements, not a new native suite run
|
|
328
|
+
for this documentation change. The release-pair baseline records
|
|
329
|
+
excellent: <!-- pf:releases[1.4.0].scoreboard.excellent|int -->7,983<!-- /pf -->;
|
|
330
|
+
strong: <!-- pf:releases[1.4.0].scoreboard.strong|int -->6<!-- /pf -->;
|
|
331
|
+
graded: <!-- pf:releases[1.4.0].scoreboard.graded|int -->7,989<!-- /pf --> probes,
|
|
332
|
+
with <!-- pf:releases[1.4.0].scoreboard.belowStrong|int -->0<!-- /pf --> below strong
|
|
333
|
+
and <!-- pf:releases[1.4.0].scoreboard.engineErrors|int -->0<!-- /pf --> engine errors.
|
|
334
|
+
These are recorded grading outcomes, not a statement that no internal attempt
|
|
335
|
+
ever failed. Baseline <!-- pf:releases[1.4.0].scoreboard.id|code -->`pineforge-parity-baseline-20261007-engine-b3192bfc`<!-- /pf -->
|
|
336
|
+
measures engine <!-- pf:releases[1.4.0].scoreboard.engineCommit|short-code -->`b3192bfc`<!-- /pf -->
|
|
337
|
+
and codegen <!-- pf:releases[1.4.0].scoreboard.codegenCommit|short-code -->`bfc4ddce`<!-- /pf -->;
|
|
338
|
+
these quantities render from the public release facts, not numeric overrides.
|
|
339
|
+
|
|
23
340
|
## 1.3.0 — 2026-10-06
|
|
24
341
|
|
|
25
342
|
A minor release: generated strategy libraries gain two receipts beside 1.2.0's
|