Existing implementation may trigger infinite cycles when collecting effects above or below the current block after wrapping around a loop-like construct. Limit this case to only looking at the immediate block (loop body). This is correct because wrap around is intended to consider effects of different iterations of the same loop and shouldn't be existing the loop block. Reported-by: Fabian Mora <fmora.dev@gmail.com> Co-authored-by: Fabian Mora <fmora.dev@gmail.com>
24 KiB
24 KiB