⚡ Simpler, faster msg-att parser (for fetch responses)
#205
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.
response-dataparser #201, but formsg-att.msg-attfrequency statistics to back up that claim) but it should definitely help to help avoid conflicts.UIDandFLAGS),MODSEQ(currently, the only supported attribute that's in neither 3501 or 9051).section,section-spec,header-list,header-fld-name.msg-attlabel forBODY[...]<...>prior to the case stmt. This greatly simplifies the code for reading attribute values, allowing much of it to be deleted.I have written support for several more fetch
msg-att, that builds on the changes in this PR:BINARYandBINARY.SIZE#207 (BINARYandBINARY.SIZE) -- also needed forIMAP4rev2EMAILIDandTHREADID#206 (for theOBJECTIDextension)X-GM-EXT-1extensions #209X-GM-MSGID,X-GM-THRID,X-GM-LABELS(nonstandard GMail extensions)ANNOTATIONPREVIEWSAVEDATE