-
Notifications
You must be signed in to change notification settings - Fork 1
SL-19314: Recast llsd serialization to write to a stream. #5
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
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
7f78b62
SL-19314: WIP: First steps towards serializing to stream, not str.
nat-goodspeed 2dc9497
SL-19314: Revert _format_datestr() to return a value.
nat-goodspeed 99f19cb
SL-19314: Recast LLSDXML[Pretty]Formatter to write to a stream.
nat-goodspeed dc753af
SL-19314: Move write() wrapper method to LLSDBaseFormatter.
nat-goodspeed 2fce8eb
SL-19314: Recast LLSDNotationFormatter to write to passed stream.
nat-goodspeed 65c047b
SL-19314: Recast serde_binary.format_binary() to write to stream.
nat-goodspeed aef973e
SL-19314: Hoist write_{binary,notation,xml,pretty_xml} into llsd.
nat-goodspeed 02cd015
SL-19314: Merge branch 'main' into sl-19314
nat-goodspeed ca0650a
SL-19314: Address code review comments.
nat-goodspeed 2bc7c2c
Merge branch 'main' into sl-19314
nat-goodspeed c9d34f2
Merge branch 'main' into sl-19314
bennettgoble ba99d6c
Merge branch 'main' into sl-19314
nat-goodspeed 2a19caf
Merge branch 'main' into sl-19314
nat-goodspeed File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Naive Q since I'm probably missing a lot of context. These were publicish methods that someone might use to generate fragments of notation format for a value before. Did nobody actually use them for such a purpose because this would break every such use? Should these all be renamed "_" (they're modifying an internal object)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have always assumed that the historical names of these methods were chosen to emphasize the communication between LLSDBaseFormatter and its subclasses. I've never seen any
llsd
consumer directly reference anyLLSDMumbleFormatter
class, never mind call its type-specific methods.That said, yes, those methods are intended solely for internal use by that class hierarchy. Perhaps they should be prefixed with an underscore. If we're going to break hypothetical consumers, better to break them overtly with
AttributeError
than by quietly returningNone
.