Lispex- Модуль
- std.
lispex → - Получатель
- Неприменимо
- Минимальное число аргументов
- 0
- Максимальное число аргументов
- 0
Declaration and parameters
СсылкаДоступность
Включено по умолчанию · Нет
Import std.lispex from an application package with a verified lock. Packages with [lispex] require --locked. Application profile topaz/ uses evaluator profile lispex/. Application profile topaz/ uses evaluator profile lispex/.
The generated-module resolver gate starts at language mode 5.18. Compatibility of this API with earlier released editions remains Pending. Target deployment conditions are native (native-only), web (web-isolated-workers), web- (web-isolated-workers). Runtime payload follows checker-reached rules. An empty reached-rule set includes no runtime payload. Application quotas are required. Lock-only packages do not receive these application modules.
Получатель
Ограничения параметров
LispexBoundaryReport identifies the phase, a stable code, named presentation fields and a human readable message. LispexReportField names and values explain the host failure. They are diagnostic presentation rather than canonical guest condition parameters.
source is Some of the exact source identity when that identity has been established and None otherwise. verified lists identities actually validated before refusal. It cannot contain a proposed program or request identity merely because the input claimed one.
A source reading or normalization failure before a canonical program exists uses a source bound report. It may identify a source location through named fields. It has no fabricated canonical program site or completed evaluation receipt.
Admission rejects unsupported contracts, missing components, identity mismatches, ambient imports and an insufficient physical execution envelope. Its report identifies the first failed check and relevant supplied component. A mismatch never selects a substitute component or smaller limits.
Host budget reports retain the submitted finite limits and first exhausted host axis in their fields. Host scheduling and physical failures describe an attempt rather than a deterministic guest resource result.
Messages, field presentation order, paths and local coordinates do not define canonical outcome identity. Programs branch on the phase and code under the selected report contract. Reading report fields performs no I/O or guest execution.
No report accessor raises a second Lispex failure. Array fields follow collection value semantics. Reading a report does not retry its failed operation, consume a guest budget or authorize an external action.
Связанное правило · Read structured reports without inventing outcomes →Результат
Эффекты
Ошибки
Result and effects
СсылкаCarry a named presentation field in a host report.
Why
СсылкаThe reports contract gives this operation one explicit input boundary and preserves the distinct result and failure cases.
Related entries
СсылкаRead structured reports without inventing outcomes
СсылкаRead structured reports without inventing outcomes
LispexBoundaryReport identifies the phase, a stable code, named presentation fields and a human readable message. LispexReportField names and values explain the host failure. They are diagnostic presentation rather than canonical guest condition parameters.
source is Some of the exact source identity when that identity has been established and None otherwise. verified lists identities actually validated before refusal. It cannot contain a proposed program or request identity merely because the input claimed one.
A source reading or normalization failure before a canonical program exists uses a source bound report. It may identify a source location through named fields. It has no fabricated canonical program site or completed evaluation receipt.
Admission rejects unsupported contracts, missing components, identity mismatches, ambient imports and an insufficient physical execution envelope. Its report identifies the first failed check and relevant supplied component. A mismatch never selects a substitute component or smaller limits.
Host budget reports retain the submitted finite limits and first exhausted host axis in their fields. Host scheduling and physical failures describe an attempt rather than a deterministic guest resource result.
Messages, field presentation order, paths and local coordinates do not define canonical outcome identity. Programs branch on the phase and code under the selected report contract. Reading report fields performs no I/O or guest execution.
No report accessor raises a second Lispex failure. Array fields follow collection value semantics. Reading a report does not retry its failed operation, consume a guest budget or authorize an external action.
Причина
A failed phase can establish some facts without completing the next phase. Keeping those verified facts separate from canonical outcomes prevents missing identities and host failures from becoming invented semantic evidence.
Read verified report facts without a guest outcome
Ссылкаimport std.bytes { Bytes }import std.lispex {LispexBoundaryReport,LispexIdentity,}function reason(report: LispexBoundaryReport) -> string {let verified: Array<LispexIdentity> = report.verifiedmatch (report.source) {case Some(source) => { let identity: LispexIdentity = source }case None() => {}}for field in (report.fields) {let name: string = field.namelet value: string = field.value}return report.code}export function main(args: Array<string>, stdin: string) -> Result<int, string> {return Ok(0)}
Нет стандартного вывода.Ожидаемый результат
Ожидаемый результат
Проверка принимает программу. Код завершения 0.
Use a verified Lispex application package supplied through TOPAZ_LISPEX_APPLICATION. This example specifies the Lispex 2.0 behavior. The product scope remains the public 5.21.3 observation scope.