-
Notifications
You must be signed in to change notification settings - Fork 7
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
can't get type def from scope by ref: entity not found: '$TYPE' #566
Comments
~Should be The syntax for import is So when you import However, error doesn't seem to be good. But with our limited resources we need to focus on happy-path now. Issue could remain with "major" status (instead of "critical" otherwise). @Catya3 please try to replace your import statement with BTW the |
testpkg was in stdlib in this case |
Yes you right, my fault |
UpdateAfter debugging with @Catya3 turns out that problem arise when we use some custom type that is defined outside of Why this is happeningWhen we call Possible solutionPass |
Will be fixed in #573 |
Fixed in #581 please merge main to your branch |
In the feature-std-image branch such struct builder code returns an error like this. It seems to be caused by the use of nested type parameters like Struct<stream<repro.Foo>> as simply Struct<repro.Foo> is not enough to trigger it. This is a minimal repro. It could have something to do with issue nevalang#566 or be subtly different. We might need the same treatment for generic frames.
I found another occurrence of this in https://github.com/nevalang/neva/tree/repro-struct-builder
|
@Catya3 please merge/rebase fresh Thank you BTW |
reopen if needed |
Describe the bug
A issue with the build/analyzer causes types in Component IO not to be fully qualified. The error is as specified in the title. It comes up when you use an external component that exports one of its types in component IO.
The stack looks like this (when the type is used as an outport):
The ultimate error comes from the analyzer.
To Reproduce
Steps to reproduce the behavior:
std/testpkg/test.neva
internal/runtime/funcs/test_component.go:
examples/testpkg/main.neva:
Expected behavior
We seemingly cannot export types in Component IO. The fix should be somewhere in the builder/analyzer.
The text was updated successfully, but these errors were encountered: