inter-target ordering - #73
Draft
pufferfish101007 wants to merge 17 commits into
Draft
pufferfish101007 wants to merge 17 commits into
pufferfish101007 wants to merge 17 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
very very WIP, nowhere near ready. creating a PR to make a note of what needs to be done.
will resolve #59
Changes
Still TODO
IntraRecGroupInfoor similar context in which to registerRecGroupDependenciesCompoundTypefor a rec group item so that rec group registrations have a canonical representation and can be registered uniquelyCompoundTypeto actual WASM type - need to encapsulate into a real rec group to reference type indices greater than the current one.TStackArrayvsTDynArray<TStackStruct>PartOfRecGrouptrait or similar, then if deps include that (byFilter), register deps then search in returned rec group for correct shapeTRecGroupItem<0>could refer to totally different types in different rec groups)StaticFunctionRegistry"overrides" within thefinishing of the registry, rather than theWasmProjectneeding to call each one out individually. Particularly important for handlingDyanmicArray*<T>ops because you can't know what'll be registered in advanceStaticFunctionRegistryso that static functions can register other funvtion at finish/registration timetyfpinto a separate crate? or make more minimal :(