본문으로 건너뛰기
토파즈6.0 · 출시 전
다운로드 →

문서 검색

명세 6.0

방향키로 결과를 고르고 Enter를 눌러 여세요.

API 이름, 진단 번호, 규칙 또는 프로젝트 주제를 입력하세요.

    진단 TPZ3007

    An imported module has a top-level runtime-bearing free statement.

    Diagnostic and cause

    링크

    Runtime statement in imported module

    계열
    topaz
    단계
    resolve
    코드
    TPZ3007

    원인과 조건

    Historical SELF behavior: an imported module containing a free top-level expression produces TPZ3007, while the same expression may occur in the entry module. The recommended Modules contract removes this file-role restriction. Its accepted entry/import pair and current-product limitation are the normative /v6.0/en/docs expectations for that decision; the reproduction below preserves the historical diagnostic identity.

    대응

    For the current SELF product, an explicit exported function called from the entry is a workaround. Under the recommended uniform module contract, no source change is required solely because a file is imported. TPZ3007 remains reserved for the historical restriction and is not reassigned.

    Compiler phase: resolve.

    Compiler explanation: An imported module has a top-level runtime-bearing free statement.

    Message templates. The marker ⟨value⟩ stands for text computed for the reported program.

    • imported module ⟨value⟩ contains a top-level free statement; free statements are entry-only (the same file is valid as an entry) Source

    Observed for the candidate in Topaz 5.21.3. Execution

    • error[TPZ3007]: imported module lib contains a top-level free statement; free statements are entry-only (the same file is valid as an entry)

    Historical SELF restriction: the imported module contains a top-level free statement, including an expression with no visible side effect. The recommended uniform module contract accepts the same statement forms in entry and imported files.

    규칙diagnostics.tpz3007.rule

    Trigger and repair

    Historical SELF behavior: an imported module containing a free top-level expression produces TPZ3007, while the same expression may occur in the entry module. The recommended Modules contract removes this file-role restriction. Its accepted entry/import pair and current-product limitation are the normative /v6.0/en/docs expectations for that decision; the reproduction below preserves the historical diagnostic identity.

    Response

    링크

    For the current SELF product, an explicit exported function called from the entry is a workaround. Under the recommended uniform module contract, no source change is required solely because a file is imported. TPZ3007 remains reserved for the historical restriction and is not reassigned.

    Reproduction and verification

    링크

    Rejected program

    링크
    example.tpzRejected program플레이그라운드 열기 →
    1. import lib
    기대 출력0이 아닌 종료 코드
    표준 출력 없음.
    $ topaz check example.tpz · 대상 제품 5.21.3
    lib.tpzRejected program플레이그라운드 열기 →
    1. export let value = 1
    2. 1 + 2
    기대 결과

    기대 결과

    거절 단계 resolve. 종료 코드가 0이 아닙니다.

    The expected diagnostic, cause, source location, and accompanying diagnostics are specified below. The verification status records whether this program has been run.

    Corrected program

    링크
    example.tpzCorrected program플레이그라운드 열기 →
    1. import lib
    기대 출력종료 코드 0
    $ topaz check example.tpz · 대상 제품 5.21.3
    lib.tpzCorrected program플레이그라운드 열기 →
    1. export function value() -> int { 1 + 2 }
    기대 결과

    기대 결과

    검사가 프로그램을 받아들입니다. 종료 코드 0.

    This program applies the repair described above. The verification status records whether it has been run.

    메뉴

    다운로드 →