From 242c0889b23ed5f4f8a29bc9c6580e5607caafbc Mon Sep 17 00:00:00 2001 From: Andrew Lenharth Date: Thu, 15 Jun 2023 14:14:33 -0500 Subject: [PATCH] [major] Disallow implicit truncation in connect --- revision-history.yaml | 1 + spec.md | 4 +--- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/revision-history.yaml b/revision-history.yaml index dfaaf360..26a79b44 100644 --- a/revision-history.yaml +++ b/revision-history.yaml @@ -19,6 +19,7 @@ revisionHistory: construction of hardware literals. - Change string-encoded integers to radix-encoded integers. - Remove legacy connect (`<=`) and invalidate (`is invalid`) syntax + - Make connect disallow implicit truncation (again). abi: - Initial ABI description. # Information about the old versions. This should be static. diff --git a/spec.md b/spec.md index 4794bebe..f3869cdf 100644 --- a/spec.md +++ b/spec.md @@ -1103,9 +1103,7 @@ In order for a connection to be legal the following conditions must hold: Connect statements from a narrower ground type component to a wider ground type component will have its value automatically sign-extended or zero-extended to -the larger bit width. Connect statements from a wider ground type component to a -narrower ground type component will have its value automatically truncated to -fit the smaller bit width. The behavior of connect statements between two +the larger bit width. The behavior of connect statements between two circuit components with aggregate types is defined by the connection algorithm in [@sec:the-connection-algorithm].