It's a sad reality that while developing modules, some of the ports will be unconnected. This prevents the compiler from giving good typechecking & latency counting info until all ports have been connected. This usually happens only right at the end of design. Perhaps, only reporting a warning and emitting randomly-chosen absolute latency values for such unconnected ports will ease development a bit.
(also, this is in line due to complaints about the unconnected ports errors being quite obtuse)
It's a sad reality that while developing modules, some of the ports will be unconnected. This prevents the compiler from giving good typechecking & latency counting info until all ports have been connected. This usually happens only right at the end of design. Perhaps, only reporting a warning and emitting randomly-chosen absolute latency values for such unconnected ports will ease development a bit.
(also, this is in line due to complaints about the unconnected ports errors being quite obtuse)