effectfully

This looks pretty severe, it's a shame there's been no action for almost a year on this issue. I'll bring it up to the team.

> Sorry, I forgot to follow up on this. We should look at the PIR and try to figure out why that happened. It's a failure of our processes, I'm...

A month later, the issue is still unassigned and hasn't been worked on yet. I just wrote another message on our private slack asking for this ticket to get prioritized....

@it4rb thank you for the report. If you have any additional info or ideas as to what we should've done differently to reproduce the issue, please let us know.

Given the huge costs > And it would need a new language version, and we'd have to support both ways, etc. and the modest benefits > I can't think of...

@thealmarty you implemented parsing of `datatypebind` and other PIR things, right? If so, please close this issue.

@thealmarty thank you. > I think it's best to close this after tests are added? Good point, let's do that.

@thealmarty do you happen to know the status of this issue?

Seems like it then! Thanks a lot, closing as resolved.

@michaelpj > That is a good point about reference scripts. > Unclear. We might have to do it for correctness, I don't know. So what about that? This seems like...