You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following class is accepted by javac, but causes the VerCors monomorphizeClass rewrite to recurse forever:
classA<T> {
A<A<T>> walker;
}
VerCors appears to hang until it crashes with a stack overflow exception. The same occurs when the snippet is parsed as PVL.
It's probably unlikely that someone would actually need or write such a class, but I would still not expect VerCors to get stuck - instead, I would expect an error message explaining that the class can not be monomorphized.
The text was updated successfully, but these errors were encountered:
I agree with your conclusion. Not sure if the added complexity of the check is proportional to the benefit of a nice error message, though... (Given the rarity of using generics like this)
The following class is accepted by
javac
, but causes the VerCorsmonomorphizeClass
rewrite to recurse forever:VerCors appears to hang until it crashes with a stack overflow exception. The same occurs when the snippet is parsed as PVL.
It's probably unlikely that someone would actually need or write such a class, but I would still not expect VerCors to get stuck - instead, I would expect an error message explaining that the class can not be monomorphized.
The text was updated successfully, but these errors were encountered: