Open DanilaFe opened 2 years ago
This seems like it has the potential to be an easy fix, but I'd be worried about having a wandering developer try to handle it if we marked it as easy.
I agree with Lydia. It shouldn't be hard for us to catch when the class management flavors are applied to non-classes. In fact, it makes me curious what would happen if that assertion were turned into a conditional that simply said something like USR_FATAL("Can't apply class management types to non-classes");
and was run through parallel testing. I can give it a shot if nobody else is already trying something similar (or wants to).
(This seemed familiar, and I think it's because of the following PR which is thematically related, but also different: https://github.com/chapel-lang/chapel/pull/18757)
Summary of Problem
I get an internal compiler error in the following code:
It originally came up when I was trying to make a list of owned records, but seems like use in any type actual will do. The error without developer mode is on line
3
(invalid code, by the way, since records cannot beowned
). In debug mode, the compiler reports the following:Steps to Reproduce
Compile command:
chpl minimal-owned-record.chpl
Configuration Information
chpl --version
:$CHPL_HOME/util/printchplenv --anonymize
: