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

Add alloc counter benchmark for result erasing maps. #1858

Merged
merged 1 commit into from May 25, 2021

Commits on May 25, 2021

  1. Add alloc counter benchmark for result erasing maps.

    Motivation:
    
    Peter thinks that result-erasing maps should not allocate, and we have
    special code paths in the code to try to make Void -> Void maps not
    allocate. Sadly, both code paths currently do allocate.
    
    Per our rules for not trying to make optimizations without data, we
    should start measuing these closures so we can make optimizations.
    
    Modifications:
    
    - Added an alloc couter test for result-erasing maps.
    
    Result:
    
    Alloc counter test suitable for any fix of apple#1697.
    Lukasa committed May 25, 2021
    Configuration menu
    Copy the full SHA
    7c076ad View commit details
    Browse the repository at this point in the history