Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update behavior around substituting Foo? into a usage of an unspec-bounded type variable #43

Open
cpovirk opened this issue Apr 25, 2023 · 0 comments

Comments

@cpovirk
Copy link
Collaborator

cpovirk commented Apr 25, 2023

...if we decide in jspecify/jspecify#248 to change it: Currently, the result is Foo?, but we're discussing changing it to Foo*.

(I suppose someone could remind us that it wouldn't be wrong for a checker to continue to produce Foo?. However, presumably that's not what we want from the reference checker: At the very least, we'd really like to be able to cross-reference the reference checker's results against the conformance tests, which will include * where appropriate!)

I started writing a longer thing here about how the changes required might go beyond what the word "substituting" might suggest. However, I've gotten myself confused, and it's the end of the week, so I'll figure it out another day. It will end up fitting better into a discussion about jspecify/jspecify#248, anyway.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant