Capture constness on elaborated types#14
Open
slburson wants to merge 2 commits into
Open
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.
I started trying to compile the generated adapter, and the first problem I ran into was that Claw was generating getter/setter functions for global variables declared const.
For example, source essentially like this (greatly simplified):
produced this output:
I traced the problem to these lines near the beginning of
resect_type_create:I wondered whether the constness was set on the elaborated type, and was therefore being lost, and this proved to be the case. Working out a fix took some time and experimentation, but I finally came up with something I'm happy with.
(I suspect this fixes the bug that you wrote
claw.resect::ensure-const-type-if-neededto work around, but I haven't checked.)The idea is that we need to use the elaborated type as the registration key so that we can safely mark the type const once it is built. This requires moving the
resect_find_typecall to the top, and replacing the recursive call with (a) noting whether the elaborated type was const, and (b) unwrapping it for the benefit of subsequent processing.