Do not use isSet in isUsed functions #655
Merged
+8
−3
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.
Please check contribution guide first.
Description
The
is*Set()
functions are generated for-withWriterCode
only, but are used withoutfurther checking in
is*Used()
which results in non compiling code if usingoptional
fields with-withoutWriterCode
.Always generateis*Set()
for optional fields.Alternative would be changing the expression, the C++, Java and Python generators generate for
optionals <type>
members to not callis*Set()
but test the optional directly.
The line triggering this bug in the
Structure*.ftl
files is (example from the Python generator, line 304):I've added an unused
optional ...
field to one of the test-structs, that triggers the bug without this change.Type of Change