-
Notifications
You must be signed in to change notification settings - Fork 94
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
Reference to constructor in module #447
Comments
Hmm, if we changed the identifier we wouldn't be able to link correctly as we wouldn't know which type the construct was in. I think the issue is probably that when we open the module containing the type declaration in |
Constructors (and fields) are already added to the env (in The current issue is in signatures ( |
I'm still not clear on what the issue is with Paths_types? |
We just need to allow "signature | datatype" parents in constructor references. |
Oh in the references! I was thinking of the identifiers :-) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. The main purpose of this is to keep the issue tracker focused to what is actively being worked on, so that the amount and variety of open yet inactive issues does not overwhelm contributors. An issue closed as stale is not rejected — further discussion is welcome in its closed state, and it can be resurrected at any time. odoc maintainers regularly check issues that were closed as stale in the past, to see if the time is right to reopen and work on them again. PRs addressing issues closed as stale are as welcome as PRs for open issues. They will be given the same review attention, and any other help. |
This is in the next milestone. |
Signed-off-by: Paul-Elliot <peada@free.fr> Co-authored-by: Paul-Elliot <peada@free.fr>
Co-authored-by: Paul-Elliot <peada@free.fr> Signed-off-by: Paul-Elliot <peada@free.fr>
Co-authored-by: Paul-Elliot <peada@free.fr> Signed-off-by: Paul-Elliot <peada@free.fr>
Co-authored-by: Paul-Elliot <peada@free.fr> Signed-off-by: Paul-Elliot <peada@free.fr>
Co-authored-by: Paul-Elliot <peada@free.fr> Signed-off-by: Paul-Elliot <peada@free.fr>
With the new model, the reference
M.Foo
doesn't resolve butM.t.Foo
does.In
Paths_types
, constructor parent should beparent
or a newconstructor_parent
instead ofdatatype
.Also, the type for references allows extension and exception constructors in
{!constructor:..}
references but won't resolve them.The text was updated successfully, but these errors were encountered: