Enhance Non-Primitive Depolorizer Methods to Handle NULL Wire #19
Conversation
This file contains 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
sarvalabs-gokul
added
bug
sarvalabs-gokul
changed the title
sarvalabs-gokul
changed the title
sarvalabs-manish
approved these changes
Feb 19, 2024
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.
Description
This pull request addresses a bug in the non-primitive methods which includes
depolorizeArray,depolorizeMap, anddepolorizeStruct. Previously, when encountering theWIRE_NULLwire type, these methods would an throw error. This update adds explicit handling for theWIRE_NULLcase, ensuring that these methods now return appropriate empty values ([] for arrays, new Map() for maps, and {} for structs) instead of errors. This aligns the behavior with the expected functionality, enhancing the robustness and reliability of the codebase.