Skip to content
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

feat: add byte slice as JSON string writer #43

Merged
merged 5 commits into from
Apr 6, 2022

Conversation

tdakkota
Copy link
Member

@tdakkota tdakkota commented Apr 5, 2022

No description provided.

@codecov
Copy link

codecov bot commented Apr 5, 2022

Codecov Report

Merging #43 (7018dd7) into main (27f88a8) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #43   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           35        36    +1     
  Lines         2306      2323   +17     
=========================================
+ Hits          2306      2323   +17     
Impacted Files Coverage Δ
byteseq.go 100.00% <100.00%> (ø)
enc_str.go 100.00% <100.00%> (ø)
w_str.go 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 27f88a8...7018dd7. Read the comment docs.

@tdakkota tdakkota force-pushed the feat/add-bytestr-writer branch from 685fc6e to 8450a01 Compare April 5, 2022 21:21
@tdakkota tdakkota marked this pull request as ready for review April 5, 2022 22:31
@tdakkota tdakkota force-pushed the feat/add-bytestr-writer branch from 8450a01 to 5ed08bb Compare April 6, 2022 02:53
@ernado ernado merged commit 0a79161 into go-faster:main Apr 6, 2022
@tdakkota tdakkota deleted the feat/add-bytestr-writer branch April 6, 2022 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants