quantize to prevent leaks with float32 #435
Merged
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.
now that we have split parsing an svg from rendering it, i'd like to focus the benchmark just on the rendering for the time being. the parsing is it's own thing to benchmark but the rendering is the vast majority of time.
before:
after:
these timings are using treeform/vmath#54
both have no leaks with fuzz_leaks.nim or fuzz_leaks2.nim
no change in output quality (we can't do more than 256 steps of aa anyway)
this does slightly change svg output so many of the test rendered files change. im not committing them here since i have other changes that will affect all files and we've talked about a different way of handling test files as well