Make Interface constructor public#354
Merged
Merged
Conversation
jessebraham
approved these changes
Feb 15, 2023
jessebraham
left a comment
jessebraham
left a comment
Member
There was a problem hiding this comment.
Seems reasonable enough, I think it was only protected because the interface module at one point was private, so this probably just never got updated. Thanks!
Contributor
Author
|
I missed it, too, when I was poking at raspberry support :) |
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
2 participants
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.
As it turns out, users (me) might actually want to construct
Interfaceobjects. While the fields are public, the raspberry-enablednewdoes a few useful things that I don't necessarily want to duplicate in my program.