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
It's probably a bad idea to put the effect on the lazy val type - it's the only place where a value has an effect annotation, and this is exactly what we try to avoid (in pluginsTyped we remove all effect annotations from terms).
Having effect annotations on values leads to all random interactions with the typer, because terms suddenly have effects, which triggers the annotationChecker.
Alternative to putting the effect on the lazy val type: put it as an attachment in the symbol. That might not work across separate compilation though.
Maybe we can put it inside another annotation which is not a TypeConstraint (@lazyValEffect(...)).
The text was updated successfully, but these errors were encountered:
It's probably a bad idea to put the effect on the lazy val type - it's the only place where a value has an effect annotation, and this is exactly what we try to avoid (in pluginsTyped we remove all effect annotations from terms).
Having effect annotations on values leads to all random interactions with the typer, because terms suddenly have effects, which triggers the annotationChecker.
Alternative to putting the effect on the lazy val type: put it as an attachment in the symbol. That might not work across separate compilation though.
Maybe we can put it inside another annotation which is not a TypeConstraint (
@lazyValEffect(...)
).The text was updated successfully, but these errors were encountered: