Skip to content

Fix the encoding of imported resources in the CompositionGraph.#74

Merged
peterhuene merged 1 commit intomainfrom
fix-resource-import
Apr 11, 2024
Merged

Fix the encoding of imported resources in the CompositionGraph.#74
peterhuene merged 1 commit intomainfrom
fix-resource-import

Conversation

@peterhuene
Copy link
Member

This PR fixes the encoding of imported resources in the CompositionGraph.

Previously a panic was encountered when the graph attempts to import, either explicitly or implicitly, a resource.

The fix requires tracking the "owner" of an aliased resource so that the export on the owning interface may be aliased and used for type equality when encoding the resource import.

Fixes #62.

This commit fixes the encoding of imported resources in the `CompositionGraph`.

Previously a panic was encountered when the graph attempts to import, either
explicitly or implicitly, a resource.

The fix requires tracking the "owner" of an aliased resource so that the export
on the owning interface may be aliased and used for type equality when encoding
the resource import.

Fixes #62.
@peterhuene peterhuene requested a review from rylev April 10, 2024 20:02
@peterhuene
Copy link
Member Author

@rylev this fixes only the CompositionGraph encoding and not the current encoding implementation in wac-parser as I'm about to rip that out.

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

Successfully merging this pull request may close these issues.

Panic when exporting a top-level function that takes a resource as an argument

2 participants