-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support no-visibility constructors in >=0.7.0 #241
Conversation
Though admittedly, since pre-0.7.0 visibility was required, but post-0.7.0 it was forbidden, anyone trying to glean rules about solidity by looking at the tests will be confused when they see a default visibility test in the with-visibility fixtures... without knowing it depends on the withContract function using >=0.7.0... But I guess that's not what the tests are for... so it seems ok. If you want to change it I will leave this branch open to edits by maintainers. |
Looking forward to this. 👍 |
This should be good to merge. Any other problems that need fixing? |
Hey @junderw, sorry for the delay (again). I'm still not convinced about the pragma approach, it seems too brittle (again, a |
That seems reasonable, but I think we should be actively alerting the user of this specific awkward instance.
I think this is the best we can do in this situation... :-/ |
Co-authored-by: Franco Victorio <victorio.franco@gmail.com>
I have squashed the commits together. The original commit structure at this point can be found here: |
(Also I have rebased on protofire master) |
Thanks! I was going to do that and then I forgot 😅
That's a great idea, thank you for doing it! |
No description provided.